royale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <>
Subject Re: Maven builds for Royale can't deploy from windows-2012-1
Date Tue, 02 Oct 2018 00:21:59 GMT
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?


´╗┐On 10/1/18, 5:08 PM, "Chris Thistlethwaite" <> 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.
    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 (
    > to transfer file: 
    > . 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

View raw message