Ok, noted. Let's not bother doing anything until it happens again. It might have been a transient problem.
Julian > On Mar 22, 2016, at 19:42, Josh Elser <[email protected]> wrote: > > Build #35 was run on jenkins-test-3d4. I'm guessing that Jenkins slave > machine is just borked. Build #36 was on H11 (one of the old "hadoop" > yahoo-provided nodes). > > If we want a quick-fix, we can just limit the slaves which the job can run on > via the normal Jenkins job configuration. > > Josh Elser wrote: >> Looks like the username/password to deploy to Nexus from the Jenkins >> server is busted. This is something that should be set up on the machine >> itself (not something we have to configure). >> >> If we continue to see it, probably something we can ask infra@ about. >> >> Julian Hyde wrote: >>> Anyone know why Jenkins would fail with the following? >>> >>> ERROR: Failed to deploy artifacts: Could not transfer artifact >>> org.apache.calcite:calcite:pom:1.8.0-20160322.015711-1 from/to >>> apache.snapshots.https >>> (https://repository.apache.org/content/repositories/snapshots): Failed >>> to transfer file: >>> https://repository.apache.org/content/repositories/snapshots/org/apache/calcite/calcite/1.8.0-SNAPSHOT/calcite-1.8.0-20160322.015711-1.pom. >>> Return code is: 401, ReasonPhrase: Unauthorized. >>> >>> Julian >>> >>>> On Mar 21, 2016, at 6:57 PM, Apache Jenkins >>>> Server<[email protected]> wrote: >>>> >>>> The Apache Jenkins build system has built Calcite-Master-JDK-1.8 >>>> (build #35) >>>> >>>> Status: Failure >>>> >>>> Check console output at >>>> https://builds.apache.org/job/Calcite-Master-JDK-1.8/35/ to view the >>>> results. >>>
