Re: Gradle publish from Jenkins slaves

Right, there is nothing to fix here. Any 'externally' managed nodes that can have external users login to the nodes can not and will not have any asf credentials placed on them. This includes all of the 'Beam' nodes. All the internally hosted and managed jenkins nodes all do not accept logins from

Re: Gradle publish from Jenkins slaves

And to be clear, I think there are two issues, and perhaps no bug nor "fix" per se. The Beam issue is https://issues.apache.org/jira/browse/BEAM-6919 but then it sounds like having an easy way to identify which agents have the needed gradle.properties file is somewhat independent (but helpful for u

Re: Gradle publish from Jenkins slaves

It looks like your other thread has a part of the answer. There's no plan to get the credentials onto external VMs as it used to, but the publish command itself could run on ASF-managed instances. Kenn On Mon, Apr 22, 2019 at 8:37 AM Antoine Toulme wrote: > Got it. Is there a ticket open to fix

Re: Gradle publish from Jenkins slaves

Got it. Is there a ticket open to fix this? Alternatively, jenkins could store the credentials and inject them in the build. Where can I get more context? > On Apr 22, 2019, at 08:08, Kenneth Knowles wrote: > > Yes, this is because previously these boxes were managed by infra using > puppet. T

Re: Gradle publish from Jenkins slaves

Yes, this is because previously these boxes were managed by infra using puppet. They published snapshots for a very long time succesfully. Infra has changed how they accept these workers, so now they are not puppetized, hence do not have the private credentials. This is a very recent change. Kenn

Re: Gradle publish from Jenkins slaves

Hey folks, Actually your build fails just like mine: https://builds.apache.org/job/beam_Release_NightlySnapshot/415/console 10:05:31 > Failed to publish publication 'mavenJava' to repository 'maven' 10:05:31> Could not

Re: Gradle publish from Jenkins slaves

Thank you both. I’m stealing that code. > On Apr 21, 2019, at 8:00 PM, Kenneth Knowles wrote: > > This job uploads snapshots: > https://github.com/apache/beam/blob/master/.test-infra/jenkins/job_Release_NightlySnapshot.groovy > > The place in Beam's Gradle build that sets up the credentials is:

Re: Gradle publish from Jenkins slaves

This job uploads snapshots: https://github.com/apache/beam/blob/master/.test-infra/jenkins/job_Release_NightlySnapshot.groovy The place in Beam's Gradle build that sets up the credentials is: https://github.com/apache/beam/blob/master/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugi

Re: Gradle publish from Jenkins slaves

I’ll take any idea. I looked at the beam builds, nothing in there seems to be uploading snapshots? It might be time to move to Maven to fit the mold. > On Apr 18, 2019, at 3:06 PM, Kenneth Knowles wrote: > > Beam pushed daily snapshots to nexus until the change where our (donated) > Jenkins ex

Re: Gradle publish from Jenkins slaves

Beam pushed daily snapshots to nexus until the change where our (donated) Jenkins executors were moved outside of Infra's purview. Beam migrated from Maven to Gradle while maintaining the functionality. I don't know if anything special had to be done. Added Yifan who I think knows the most about th

Gradle publish from Jenkins slaves

Hello all, I have managed to push to repository.apache.org a snapshot from my machine and want to automate this as part of CI. It looks like Maven is leveraging the ~/.m2/settings.xml file which contains the credentials of the Jenkins user to push binaries to the snapshot repository. Is that c