Also, I don't have the permissions on Jenkins here, so I can't update the config, either.
On 23 April 2016 at 17:26, Matt Sicker <boa...@gmail.com> wrote: > The test instances look like something Infra is working on to making > cloud-hosted jenkins slaves. I found some info here: > > https://cwiki.apache.org/confluence/display/INFRA/Update+Jenkins+Cloud+Nodes > > Also, this ticket looks related: > https://issues.apache.org/jira/browse/INFRA-11543 > > On 23 April 2016 at 17:07, Gilles <gil...@harfang.homelinux.org> wrote: > >> On Sat, 23 Apr 2016 14:56:23 -0500, Matt Sicker wrote: >> >>> You can blacklist jenkins slaves in the build config. Add >>> "!jenkins-cloud-4GB&&(ubuntu)" >>> to blacklist all the test instances. >>> >> >> What are the "test instances"? >> >> I don't have the privileges to modify the Jenkins configuration. >> Can you make the change to fix the authentication problem? >> >> Regards, >> Gilles >> >> >> On 23 April 2016 at 12:14, Rob Tompkins <chtom...@gmail.com> wrote: >>> >>> Honestly this seems to be an issue with the maven settings.xml on the >>>> server that ran the build. I’m guess that they were using the default >>>> maven >>>> settings.xml as opposed to the settings.xml that is needed for apache >>>> commons (which would contain the hashed credentials for the >>>> repository.apache.org <http://repository.apache.org/> nexus instance). >>>> So >>>> as stated theres not much we could do other than potentially ensuring >>>> that >>>> the build runs on a different jenkins server. >>>> >>>> -Rob >>>> >>>> > On Apr 23, 2016, at 5:59 AM, Gilles <gil...@harfang.homelinux.org> >>>> wrote: >>>> > >>>> > On Fri, 22 Apr 2016 20:08:54 -0500, Matt Sicker wrote: >>>> >> I think that's a problem with the jenkins-test-* servers. I asked >>>> infra >>>> >> about a similar issue on Log4j2, and they said that the test jenkins >>>> >> servers are not stable yet. >>>> > >>>> > Thanks for the information; so nothing to do, I guess. >>>> > >>>> > Gilles >>>> > >>>> >> On 22 April 2016 at 05:55, Gilles <gil...@harfang.homelinux.org> >>>> wrote: >>>> >> >>>> >>> On Fri, 22 Apr 2016 02:19:57 +0000 (UTC), Apache Jenkins Server >>>> wrote: >>>> >>> >>>> >>>> The Apache Jenkins build system has built Commons Math >>>> >>>> DeveloperBranch (build #7) >>>> >>>> >>>> >>>> Status: Failure >>>> >>>> >>>> >>>> Check console output at >>>> >>>> https://builds.apache.org/job/Commons%20Math%20DeveloperBranch/7/ >>>> to >>>> >>>> view the results. >>>> >>>> >>>> >>> >>>> >>> See >>>> >>> >>>> >>>> https://builds.apache.org/job/Commons%20Math%20DeveloperBranch/7/console >>>> >>> >>>> >>> The upload of the snapshot generates an error >>>> >>> Could not transfer artifact >>>> >>> org.apache.commons:commons-math4:jar:4.0-20160422.021942-574 from/to >>>> >>> apache.snapshots.https >>>> >>> Return code is: 401, ReasonPhrase: Unauthorized. >>>> >>> >>>> >>> Strangely, snapshot files with another basename have been created >>>> >>> in the snapshot area at >>>> >>> >>>> >>> >>>> >>>> >>>> https://repository.apache.org/content/repositories/snapshots/org/apache/commons/commons-math4/4.0-SNAPSHOT/ >>>> >>> e.g. >>>> >>> commons-math4-4.0-20160422.002002-573.jar Fri Apr 22 00:20:02 >>>> UTC >>>> >>> 2016 2055161 >>>> >>> >>>> >>> The above failure resulted in the build marked "Failure" whereas >>>> >>> there is no problem in the code (all tests pass now). >>>> >>> >>>> >>> Thanks, >>>> >>> Gilles >>>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > > -- > Matt Sicker <boa...@gmail.com> > -- Matt Sicker <boa...@gmail.com>
