Re: Maven builds for Royale can't deploy from windows-2012-1

[Alex Harui]

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&amp;data=02%7C01%7Caharui%40adobe.com%7C11bff50f77ed4594b64e08d627fb26d6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740356973401005&amp;sdata=HQIUXCHPQm8yqRYC5%2FFCmlFezI6Eo02CTB4phYPHbs0%3D&amp;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&amp;data=02%7C01%7Caharui%40adobe.com%7C11bff50f77ed4594b64e08d627fb26d6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740356973401005&amp;sdata=pwqSkAVxJdlDjylqLrbWnh8ZQZkIic1Ow%2B1QI5bLtck%3D&amp;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
    >