Yes, I’m doing some testing with dummy credentials. So expect some more failed release steps…
From: Alex Harui<mailto:[email protected]> Sent: Tuesday, July 14, 2020 8:55 AM To: [email protected]<mailto:[email protected]> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing! I have a vague recollection of removing credentials. But also, I think the Maven/Nexus credentials might have been stored in a password manager when we last release compiler-build-tools. You may have run Maven from the command line and typed in credentials and they got stored. Later, we replaced the tokens that result in using the password manager in settings.xml with rm.username and rm.password so we can run Ant jobs on the CI from the command prompt. But we haven't tried passing in a password from Jenkins into Maven. I'd recommend trying on a test job before trying it on these jobs to make sure the credentials don’t end up in the logs. -Alex On 7/13/20, 9:51 PM, "Yishay Weiss" <[email protected]> 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&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=cUo9%2F33M4SatU1m17xSuem08x4CkDCIMbRryPOYNvq4%3D&reserved=0 [INFO] push url: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyishayw%40gitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.git&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=cUo9%2F33M4SatU1m17xSuem08x4CkDCIMbRryPOYNvq4%3D&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&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=Z3OkzFb65IgqJAPzzpbwTZ7fzk9jA0iOI5ID8FXq2zU%3D&reserved=0 From: Alex Harui<mailto:[email protected]> Sent: Monday, July 13, 2020 8:25 PM To: [email protected]<mailto:[email protected]> Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing! On 7/13/20, 9:32 AM, "Harbs" <[email protected]> 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 <[email protected]> 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" <[email protected]> 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&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=i%2FOkZOey8GSPknCmBV5wPtugIj3GFRHBd4EqhoeVHaw%3D&reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=i%2FOkZOey8GSPknCmBV5wPtugIj3GFRHBd4EqhoeVHaw%3D&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&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=2QojWSMN1QzB1wGyXNr8d15fN7ah7%2FXinHtV8qbYSwc%3D&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&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=2QojWSMN1QzB1wGyXNr8d15fN7ah7%2FXinHtV8qbYSwc%3D&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, [email protected] 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&data=02%7C01%7Caharui%40adobe.com%7C057e1459041148c9cc4208d827b19ec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637302991109237647&sdata=A6xf6qyGH0s35rSUDbDx2wHWuwvdv0vBsGkIz48V%2F2Y%3D&reserved=0 to view the results. > > >
