I’m going to try to change the job on Jenkins so it accepts Apache credentials 
as params and propagates them to the mvn command. I don’t know if Jenkins forms 
have a password element that hides the password though.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Monday, July 13, 2020 8:34 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still 
Failing!

Another option is to find a way for Jenkins to securely pass the credentials to 
maven without it showing up in the logs.  Yishay I think found a way to do that 
with Ant, but not sure about Jenkins jobs.

HTH,
-Alex

On 7/13/20, 10:25 AM, "Alex Harui" <aha...@adobe.com.INVALID> wrote:



    On 7/13/20, 9:32 AM, "Harbs" <harbs.li...@gmail.com> wrote:

        I’m trying to wrap my head around all the pieces here.

        How does the uploading to the nexus server work?

    It doesn't.  After some snooping through the archives, I think that some 
credentials were (unsafely) stored on the CI Server.  The archives indicate 
that after build-tools was released, we tried another way of setting 
credentials for the main Royale build and that resulted in build-tools not 
being able to directly upload to nexus anymore.  Of course, I could be 
misreading the archives.

    The main Royale release prevents the upload and the RM downloads the build 
results, verifies them, and uploads them.  Someone would have to replicate that 
for build-tools.

    Other options are:
    A) to run Maven on CI and try the new Ant script that hides passwords that 
Yishay created
    B) Run the build locally.

    HTH,
    -Alex


        > On Jul 13, 2020, at 7:21 PM, Alex Harui <aha...@adobe.com.INVALID> 
wrote:
        >
        > IMO, step 1 went sideways.  The tag should not contain SNAPSHOT in 
the POM version.  Compare the tag from 1.2.0.
        >
        > Maven should also not be adding a timestamp to the artifact name.  I 
don't remember why it does that, but I think there are internet articles about 
it.
        >
        > Comparing output of successful jobs might shed some light on where 
things are going wrong.
        >
        > HTH,
        > -Alex
        >
        > On 7/13/20, 12:41 AM, "Harbs" <harbs.li...@gmail.com> wrote:
        >
        >    It’s still having issues:
        >
        >    [INFO] [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on 
project compiler-build-tools: Failed to deploy artifacts: Could not transfer 
artifact 
org.apache.royale.compiler:compiler-build-tools:jar:1.2.1-20200713.073309-2 
from/to apache.snapshots.https 
(https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&amp;data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&amp;sdata=4hwVFzmW8JXfy6z838X7aVsP9RXpzMEhGjDOta5ahtY%3D&amp;reserved=0
 
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&amp;data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&amp;sdata=4hwVFzmW8JXfy6z838X7aVsP9RXpzMEhGjDOta5ahtY%3D&amp;reserved=0>):
 Failed to transfer file 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&amp;data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&amp;sdata=veQ9LjfFpTz2%2BufQ8JwxOuyQLyxo%2FS8JUVvGwkZAsmM%3D&amp;reserved=0
 
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots%2Forg%2Fapache%2Froyale%2Fcompiler%2Fcompiler-build-tools%2F1.2.1-SNAPSHOT%2Fcompiler-build-tools-1.2.1-20200713.073309-2.jar&amp;data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&amp;sdata=veQ9LjfFpTz2%2BufQ8JwxOuyQLyxo%2FS8JUVvGwkZAsmM%3D&amp;reserved=0>
 with status code 401 -> [Help 1]
        >
        >    I’m kind of stuck on this. Any suggestions would help.
        >
        >    Thanks.
        >
        >> On Jul 13, 2020, at 10:33 AM, apacheroyal...@gmail.com wrote:
        >>
        >> Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still 
Failing:
        >>
        >> Check console output at 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2F15%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C2a6c6127ed734987e2e508d82751c7d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302579487383171&amp;sdata=H3xwVjFh3bAhOGsfHM6KJEm7BigUmRKhIUfUzX3g%2FkI%3D&amp;reserved=0
 to view the results.
        >
        >
        >




Reply via email to