Hi Chris,
I guess we should assume that C:\.m2\settings.xml exists, otherwise our builds
probably would have failed saying that file doesn't exist. Before you go
delete it, can you check its contents? I switched our builds to use
C:/Users/Jenkins/.m2/settings.xml and the first build got past the deploy to
repository.a.o, but now died in some Sonar thing. I'm wondering if
C:\.m2\settings.xml contains some Sonar configuration we expected to use. Can
any settings from C:\.m2\settings.xml be merged into
C:/Users/Jenkins/.m2/settings.xml? The second build is still running, but
looks like it got past the deploy to repository.a.o as well.
Thanks,
-Alex
On 10/1/18, 5:29 PM, "Chris Thistlethwaite" <chr...@apache.org> wrote:
No, the file that's under Puppet is C:/Users/Jenkins/.m2/settings.xml,
here is the line in the config
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Finfrastructure-puppet%2Fblob%2F5f15dc612c273d9a453bebcf7358783147fff38b%2Fenvironments%2Fwindows%2Fmodules%2Fjenkins_slave_windows%2Fmanifests%2Finit.pp%23L153&data=02%7C01%7Caharui%40adobe.com%7C61528ffd150d444cef6b08d627fe1c62%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740369680148652&sdata=xO2wG1OBHJki9x8EimAoYTvZ2yW5ElVx62RMh8BLYMo%3D&reserved=0
I have no clue how that would've worked before, I don't recall having
the file on C:\.m2, but half of the Windows nodes were setup manually
so there might be a lingering config here or there. win2016-2 and
win2106-3 were setup using automation and moving forward it would be
under location in Puppet.
-Chris T.
On Tue, 2018-10-02 at 00:21 +0000, Alex Harui wrote:
> Hi Chris,
>
> I started another build and it failed with the same issue. The build
> on 9/28 succeeded. The next build was on 9/30 and failed. We've
> only had failures since. I didn't report it sooner because I figured
> other Maven builds would have the same issue and someone would have
> figured it out.
>
> I think I have a clue though. Royale has 3 Maven jobs. Royale-
> framework and Royale-typedefs are failing. Royale-compiler is
> succeeding. One difference I noticed is that the failing builds are
> picking up settings from C:\.m2\settings.xml
>
> Does that file contain the password?
>
> HTH,
> -Alex
>
> On 10/1/18, 5:08 PM, "Chris Thistlethwaite" <chr...@apache.org>
> wrote:
>
> I've updated the password for repository.a.o last week and it's
> correct
> on disk. Dollars to donuts the node needed bounced to pick up the
> new
> creds. I went through and bounced the nodes when there weren't
> any
> builds, maybe an hour or so ago. Please kick of another build and
> we
> can troubleshoot from there.
>
> Thanks,
> Chris T.
>
> On Mon, 2018-10-01 at 21:23 +0000, Alex Harui wrote:
> > Hi builds@,
> >
> > We've been getting this "Unauthorized" error for several builds
> now:
> >
> > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-
> deploy-
> > plugin:2.8.2:deploy (default-deploy) on project royale-
> framework-
> > parent: Failed to deploy artifacts: Could not transfer artifact
> > org.apache.royale.framework:royale-framework-parent:pom:0.9.4-
> > 20181001.211743-107 from/to apache.snapshots.https (
> >
>
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C61528ffd150d444cef6b08d627fe1c62%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740369680148652&sdata=KC%2FqThNgfQhiZ1pOoPXEMtN13boyzZ7Tue6LjTBt3uw%3D&reserved=0
> ): Failed
> > to transfer file:
> >
>
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fframework%2Froyale-framework-parent%2F0.9.4-SNAPSHOT%2Froyale-framework-parent-0.9.4-20181001.211743-107.pom&data=02%7C01%7Caharui%40adobe.com%7C61528ffd150d444cef6b08d627fe1c62%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740369680148652&sdata=RJmfLLZ2RJz33eyr3bFqL%2B2TRnpBaghb4o%2BM12A%2BKYY%3D&reserved=0
> > . Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]
> >
> > Is this a configuration issue with our builds or a problem with
> the
> > node itself?
> >
> > Thanks,
> > -Alex
> >
>
>
>
