I guess it depends on the definition of "trivial".  I'm not sure if the Maven 
runner does a whole bunch of stuff or not that couldn't be done in a script.  
Looking at the console output, it looks like it just runs "mvn".   Some of the 
current jobs do use a script for other things if you want a starting point for 
a script.

On the other hand, I found this: https://plugins.jenkins.io/mask-passwords/
Maybe that will work.

I'm done for tonight.  Good luck,
-Alex

On 7/14/20, 12:23 AM, "Yishay Weiss" <yishayj...@hotmail.com> wrote:

    
    >But we haven't tried passing in a password from Jenkins into Maven.
    I’m not sure it’s possible to do trivially. These guys [1] want us to 
create a script snippet, but as I understand it we’re not using a script to 
invoke Maven.
    [1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.cloudbees.com%2Fhc%2Fen-us%2Farticles%2F203802500-Injecting-Secrets-into-Jenkins-Build-Jobs&amp;data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135753042&amp;sdata=X9RYMm4Jd7iRdagCyTC01EXtfnOcz3BW%2F007ksYXqUQ%3D&amp;reserved=0
    
    On 7/13/20, 9:51 PM, "Yishay Weiss" <yishayj...@hotmail.com> wrote:
    
        I don’t recall removing credentials the CI server. The last successful 
build [2] shows I was the one who performed that step. One thing I couldn’t 
understand was how come these lines have my name in them [1]. Where does 
yishayw get retrieved from?
    
    
        [INFO] fetch url: 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&amp;data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135753042&amp;sdata=sljIairDHFp1cWbtM2N8rujQ15r2BSSxCMMVJmnXxs4%3D&amp;reserved=0
    
        [INFO] push url: 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&amp;data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&amp;sdata=rvg8Z8oEcIbjPp32c5QyWkV6k6AKjmrM%2BJAPZw%2FiOaA%3D&amp;reserved=0
    
    
        [2] 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Compiler_Build_Tools_Release_Step_002%2FlastSuccessfulBuild%2Fconsole&amp;data=02%7C01%7Caharui%40adobe.com%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&amp;sdata=wMGekpW2aORwIDZ3iOY7g0kWgOZDVfHyBH%2Fdh%2FSEsRo%3D&amp;reserved=0
    
        From: Alex Harui<mailto:aha...@adobe.com.INVALID>
        Sent: Monday, July 13, 2020 8:25 PM
        To: dev@royale.apache.org<mailto:dev@royale.apache.org>
        Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 
- Still Failing!
    
    
    
        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%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&amp;sdata=GGqxC6G%2FNcGJqjkJgxvH1Yhmq0hWdIpx%2BFHBNJIBAew%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%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&amp;sdata=GGqxC6G%2FNcGJqjkJgxvH1Yhmq0hWdIpx%2BFHBNJIBAew%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%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&amp;sdata=%2Fpo3WE8CbWq7K824N6cjc9BSIcNL36N8SAJzMIQ4QjY%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%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&amp;sdata=%2Fpo3WE8CbWq7K824N6cjc9BSIcNL36N8SAJzMIQ4QjY%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%7Ca58254b69ccf41502fb108d827c6cfe8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637303082135763030&amp;sdata=fQReWVWqZEfIJB909eB%2By96%2BgOo9PFZLXoOfloDxj9U%3D&amp;reserved=0
 to view the results.
            >
            >
            >
    
    
    
    
    
    

Reply via email to