Cool! I didn't know Ant could hide the password. You are welcome to add a task to releasesteps that can run on the CI and see If it will upload all of the artifacts with fewer or zero failures.
-Alex On 4/28/20, 10:06 AM, "Yishay Weiss" <[email protected]> wrote: This ant script worked for me (password is typed but not shown). <?xml version="1.0"?> <project default="main"> <target name="getServerCredentials"> <input message="user:" addproperty="server.user" /> <input message="password:" addproperty="server.pass"> <handler classname="org.apache.tools.ant.input.SecureInputHandler" /> </input> </target> <target name="main" depends="getServerCredentials"> <echo>user: ${server.user} password: ${server.pass}</echo> </target> </project> From: Alex Harui<mailto:[email protected]> Sent: Tuesday, April 28, 2020 7:46 PM To: [email protected]<mailto:[email protected]> Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails Don't know what the best workflow is until we try a few things. There are at least two workflows: 1) Upload the artifacts from CI and RM uploads only the asc files as you suggested 2) RM uploads asc files to the CI server and everything gets uploaded to staging from CI. I have a hunch that there is something funky about the staging server and Wagon such that they don't get along. We've had similar problems with the Flex SDK Installer downloading things as well. If you think about it, don't you upload and download tons of stuff to Git and other places without failures as frequently? So it may be that we end up at #2, because we find that you can upload all of the ASC files to the CI server reliably but not to Staging. But first we need a secure way to type in your password on the CI server before we can find out. -Alex On 4/28/20, 1:57 AM, "Yishay Weiss" <[email protected]> wrote: I think it should be possible to do this in powershell, with: $password = Read-Host "Enter Password" -AsSecureString And pass $pass as the param. Are you suggesting to upload the .asc files separately from the local computer? From: Alex Harui<mailto:[email protected]> Sent: Tuesday, April 28, 2020 9:29 AM To: [email protected]<mailto:[email protected]> Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails I think I have found a way to get the CI Server to upload the artifacts without storing credentials on the CI server. The settings.xml file has the following entries for the servers: <username>${rm.username}</username> <password>${rm.password}</password> Now we need a secure way to have the RM enter their Apache password and run a command like: mvn wagon:upload -Drm.username=... -Drm.password=... ... I tested it by typing my password on the command line but it is visible. That is a bit risky in case someone else logs in and kicks you off RDP. Does someone know PowerShell and can come up with a script that asks for the password and hides it and passes it on to Maven without making it visible? There are some articles on doing it in .BAT but they seem like a hack. I suppose we could write an AIR app that does it or some other Windows EXE? Or install a Bash shell. Thoughts? -Alex On 4/27/20, 10:09 PM, "Alex Harui" <[email protected]> wrote: We are currently using org.codehaus.mojo's wagon-maven-plugin 2.0.0. There is an org.apache.maven.wagon.Wagon that is at 3.4.0. I think we can switch to that by replacing the wagon entry in the royale-asjs pom.xml <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>wagon-maven-plugin</artifactId> <version>2.0.0</version> <configuration> <includes>**</includes> <serverId>apache.releases.https</serverId> <url>https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fservice%2Flocal%2Fstaging%2Fdeploy%2Fmaven2&data=02%7C01%7Caharui%40adobe.com%7Ce7881e9e072344c4790c08d7eb967421%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236903737744524&sdata=qukPjPu3oov5%2BeTXfVb%2BTSyM0I8YzU0uRJAzyyjGE2w%3D&reserved=0</url> </configuration> </plugin> Would become something like: <plugin> <groupId>org.apache.maven.wagon </groupId> <artifactId>wagon</artifactId> <version>3.4.0</version> <configuration> <includes>**</includes> <serverId>apache.releases.https</serverId> <url>https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fservice%2Flocal%2Fstaging%2Fdeploy%2Fmaven2&data=02%7C01%7Caharui%40adobe.com%7Ce7881e9e072344c4790c08d7eb967421%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236903737744524&sdata=qukPjPu3oov5%2BeTXfVb%2BTSyM0I8YzU0uRJAzyyjGE2w%3D&reserved=0</url> </configuration> </plugin> HTH, -Alex On 4/27/20, 1:46 PM, "Alex Harui" <[email protected]> wrote: Don't see Wagon 3.4.0 on Central. I do see Wagon Providers 3.4.0. How would we get the Wagon we use to use Wagon Providers? When the upload fails, Yishay is not given a away to start from the point of failure ("maven -rf ..."). I have suggested using Wagon to upload individual folders -Alex On 4/27/20, 3:07 AM, "Christofer Dutz" <[email protected]> wrote: Hi all, a week ago a new version of Wagon was released ... perhaps worth updating to 3.4.0? Chris Am 27.04.20, 11:58 schrieb "Yishay Weiss" <[email protected]>: Awesome ________________________________ From: [email protected] <[email protected]> Sent: Monday, April 27, 2020 8:56:00 AM To: [email protected] <[email protected]> Subject: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails This is an automated email from the ASF dual-hosted git repository. aharui pushed a commit to branch release/0.9.7 in repository https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.git&data=02%7C01%7Caharui%40adobe.com%7Ce7881e9e072344c4790c08d7eb967421%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236903737744524&sdata=h39UeX5nPOB3FMviC6gDhRQRG9%2FPx%2B%2FOkxOuFO6j7eA%3D&reserved=0 The following commit(s) were added to refs/heads/release/0.9.7 by this push: new adeb2e3 add retry task if wagon fails adeb2e3 is described below commit adeb2e3782b59342d9132adccaf357aeece32475 Author: Alex Harui <[email protected]> AuthorDate: Sun Apr 26 22:55:41 2020 -0700 add retry task if wagon fails --- releasesteps.xml | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/releasesteps.xml b/releasesteps.xml index 729a6fc..d0f3f0a 100644 --- a/releasesteps.xml +++ b/releasesteps.xml @@ -836,6 +836,23 @@ <arg value="_releasesteps-upload-release-to-staging" /> </exec> </target> + <target name="retryUploadSWCs" depends="get-artifact-folder" description="upload all SWCs except Jewel Themes"> + <fail message="release.version not specified" + unless="release.version"/> + <fail message="rf_arg not specified" + unless="rf_arg"/> + <exec executable="${mvn}" dir="${artifactfolder}/sources" failonerror="true" > + <arg value="wagon:upload" /> + <arg value="-X" /> + <arg value="-rf" /> + <arg value="${rf_arg}" /> + <arg value="-Dwagon.fromDir=${artifactfolder}/artifacts/archive/target/local-release-dir" /> + <!--arg value="-Dwagon.includes=**" /> + <arg value="-Dwagon.excludes=**/Jewel-Dark*/**,**/Jewel-Light*/**" /--> + <arg value="-P" /> + <arg value="_releasesteps-upload-release-to-staging" /> + </exec> + </target> <target name="uploadJewelDark" depends="get-artifact-folder" description="upload Jewel Dark Themes"> <fail message="release.version not specified" unless="release.version"/>
