Let's keep the "should" conversation separate from the "how" conversation.
*On should: * I understand that it worked in the past and then stopped working. I still think it is appropriate to confirm people are comfortable with enabling it again. *On how:* Vladimir, the github workflow job is configured to use ASF provided credentials, as standard per other ASF projects that push using Github workflows. My notes in the original post called out that this PR already works on the ASF repo. (The INFRA ticket linked to https://issues.apache.org/jira/browse/CALCITE-4934, https://issues.apache.org/jira/browse/INFRA-22601 enabled the credentials.) Where is -Pasf defined/documented? What are the credentials it is using (I'm assuming it is an env variable)? On Sun, Dec 12, 2021 at 9:36 PM Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > Jacques, which credentials are you going to supply to publish the snapshots > to the ASF repository from GitHub? > > While I agree with moving towards GitHub actions, I would like to minimize > the use of ASF credentials in non-ASF environments. > > Luckily, ASF infra supplies the relevant credentials for publishing to ASF > Nexus, > so a mere "./gradlew -Pasf publish" at ASF Jenkins is enough to publish the > snapshots. > > Stamatis>In the past we used to have Jenkins jobs doing this > > The job was there, so we don't really need to discuss or vote on that. > I've created the corresponding Jenkins job here: > https://ci-builds.apache.org/job/Calcite/job/Calcite-snapshots/ > > It pulls GitHub every 5 minutes. > I am not sure if GitHub webhook integration would trigger the build (it > might need a config from INFRA), however, it is possible as well. > > Vladimir >
