Hey folks,

Actually your build fails just like mine:
https://builds.apache.org/job/beam_Release_NightlySnapshot/415/console 
<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 write to resource 
'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-vendor-sdks-java-extensions-protobuf/2.13.0-SNAPSHOT/beam-vendor-sdks-java-extensions-protobuf-2.13.0-20190421.100528-1.jar
 
<https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-vendor-sdks-java-extensions-protobuf/2.13.0-SNAPSHOT/beam-vendor-sdks-java-extensions-protobuf-2.13.0-20190421.100528-1.jar>'.
10:05:31       > Could not PUT 
'https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-vendor-sdks-java-extensions-protobuf/2.13.0-SNAPSHOT/beam-vendor-sdks-java-extensions-protobuf-2.13.0-20190421.100528-1.jar
 
<https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-vendor-sdks-java-extensions-protobuf/2.13.0-SNAPSHOT/beam-vendor-sdks-java-extensions-protobuf-2.13.0-20190421.100528-1.jar>'.
 Received status code 401 from server: Unauthorized

It looks like your last green build was Feb 29, on a slave that is disconnected 
now.


> On Apr 21, 2019, at 10:46 PM, Antoine Toulme <anto...@toulme.name> wrote:
> 
> Thank you both. I’m stealing that code.
> 
>> On Apr 21, 2019, at 8:00 PM, Kenneth Knowles <k...@apache.org> 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:
>> https://github.com/apache/beam/blob/master/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy#L573
>> 
>> Kenn
>> 
>> On Sun, Apr 21, 2019 at 4:45 PM Antoine Toulme <anto...@toulme.name> wrote:
>> 
>>> 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 <k...@apache.org> wrote:
>>>> 
>>>> 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 this.
>>>> 
>>>> Kenn
>>>> 
>>>> On Wed, Apr 17, 2019 at 10:23 AM Antoine Toulme <anto...@toulme.name>
>>> wrote:
>>>> 
>>>>> 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 correct?
>>>>> If so, is there any way I can leverage that file? I would read the XML
>>> and
>>>>> extract the credentials, but I’m pretty sure you used a symmetric key to
>>>>> encrypt the LDAP password.
>>>>> 
>>>>> Are there other projects using Gradle to push binaries to nexus?
>>>>> 
>>>>> Cheers,
>>>>> 
>>>>> Antoine
>>> 
>>> 
> 

Reply via email to