You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Yishay Weiss <yi...@hotmail.com> on 2020/04/27 09:58:36 UTC
RE: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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://gitbox.apache.org/repos/asf/royale-asjs.git
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 <ah...@apache.org>
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"/>
RE: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Yishay Weiss <yi...@hotmail.com>.
I just tried it and it seems to be working. It looks like you need to be past a certain stage before “Try mvn "<goals>" -rf :royale-typedefs-googlemaps” appears. Hopefully it’ll work as intended.
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Monday, April 27, 2020 6:29 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
Looks right to me. We won't know for sure until you actually try it.
On 4/27/20, 7:06 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Actually, I think I got the syntax wrong here. If you see an error message such as
“Try mvn "<goals>" -rf :royale-typedefs-googlemaps”
Then you should do
ant -f releasesteps.xml retryUploadSWCs -Drf_arg=:royale-typedefs-googlemaps
Where :royale-typedefs-googlemaps serves here as an example, but should be replaced with whatever the error message specifies.
Alex, please verify I got this right.
> ant -f releasesteps.xml retryUploadSWCs
>
> And that should continue the upload from the point it failed.
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Looks right to me. We won't know for sure until you actually try it.
On 4/27/20, 7:06 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
Actually, I think I got the syntax wrong here. If you see an error message such as
“Try mvn "<goals>" -rf :royale-typedefs-googlemaps”
Then you should do
ant -f releasesteps.xml retryUploadSWCs -Drf_arg=:royale-typedefs-googlemaps
Where :royale-typedefs-googlemaps serves here as an example, but should be replaced with whatever the error message specifies.
Alex, please verify I got this right.
> ant -f releasesteps.xml retryUploadSWCs
>
> And that should continue the upload from the point it failed.
RE: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Yishay Weiss <yi...@hotmail.com>.
Actually, I think I got the syntax wrong here. If you see an error message such as
“Try mvn "<goals>" -rf :royale-typedefs-googlemaps”
Then you should do
ant -f releasesteps.xml retryUploadSWCs -Drf_arg=:royale-typedefs-googlemaps
Where :royale-typedefs-googlemaps serves here as an example, but should be replaced with whatever the error message specifies.
Alex, please verify I got this right.
> ant -f releasesteps.xml retryUploadSWCs
>
> And that should continue the upload from the point it failed.
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Piotr Zarzycki <pi...@gmail.com>.
That's definitely a progress!
pon., 27 kwi 2020 o 14:21 Yishay Weiss <yi...@hotmail.com> napisał(a):
> Well, the reason I was happy was because it should now be possible to do
>
> ant -f releasesteps.xml retryUploadSWCs
>
> And that should continue the upload from the point it failed.
>
> From: Piotr Zarzycki<ma...@gmail.com>
> Sent: Monday, April 27, 2020 3:13 PM
> To: Apache Royale Development<ma...@royale.apache.org>
> Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
> wagon fails
>
> Yishay,
>
> In the other words you experienced same issue as me and others on
> Windows... Nothing changed.
>
> On Mon, Apr 27, 2020, 12:21 PM Yishay Weiss <yi...@hotmail.com>
> wrote:
>
> > I don’t know. My struggles have been with connection timeouts on uploads,
> > do you think they have improved this?
> >
> > From: Christofer Dutz<ma...@c-ware.de>
> > Sent: Monday, April 27, 2020 1:07 PM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task
> if
> > wagon fails
> >
> > 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" <yi...@hotmail.com>:
> >
> > Awesome
> >
> > ________________________________
> > From: aharui@apache.org <ah...@apache.org>
> > Sent: Monday, April 27, 2020 8:56:00 AM
> > To: commits@royale.apache.org <co...@royale.apache.org>
> > 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://gitbox.apache.org/repos/asf/royale-asjs.git
> >
> >
> > 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 <ah...@apache.org>
> > 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"/>
> >
> >
> >
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
RE: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Yishay Weiss <yi...@hotmail.com>.
Well, the reason I was happy was because it should now be possible to do
ant -f releasesteps.xml retryUploadSWCs
And that should continue the upload from the point it failed.
From: Piotr Zarzycki<ma...@gmail.com>
Sent: Monday, April 27, 2020 3:13 PM
To: Apache Royale Development<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
Yishay,
In the other words you experienced same issue as me and others on
Windows... Nothing changed.
On Mon, Apr 27, 2020, 12:21 PM Yishay Weiss <yi...@hotmail.com> wrote:
> I don’t know. My struggles have been with connection timeouts on uploads,
> do you think they have improved this?
>
> From: Christofer Dutz<ma...@c-ware.de>
> Sent: Monday, April 27, 2020 1:07 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
> wagon fails
>
> 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" <yi...@hotmail.com>:
>
> Awesome
>
> ________________________________
> From: aharui@apache.org <ah...@apache.org>
> Sent: Monday, April 27, 2020 8:56:00 AM
> To: commits@royale.apache.org <co...@royale.apache.org>
> 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://gitbox.apache.org/repos/asf/royale-asjs.git
>
>
> 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 <ah...@apache.org>
> 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"/>
>
>
>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Piotr Zarzycki <pi...@gmail.com>.
Yishay,
In the other words you experienced same issue as me and others on
Windows... Nothing changed.
On Mon, Apr 27, 2020, 12:21 PM Yishay Weiss <yi...@hotmail.com> wrote:
> I don’t know. My struggles have been with connection timeouts on uploads,
> do you think they have improved this?
>
> From: Christofer Dutz<ma...@c-ware.de>
> Sent: Monday, April 27, 2020 1:07 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
> wagon fails
>
> 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" <yi...@hotmail.com>:
>
> Awesome
>
> ________________________________
> From: aharui@apache.org <ah...@apache.org>
> Sent: Monday, April 27, 2020 8:56:00 AM
> To: commits@royale.apache.org <co...@royale.apache.org>
> 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://gitbox.apache.org/repos/asf/royale-asjs.git
>
>
> 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 <ah...@apache.org>
> 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"/>
>
>
>
RE: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Yishay Weiss <yi...@hotmail.com>.
I don’t know. My struggles have been with connection timeouts on uploads, do you think they have improved this?
From: Christofer Dutz<ma...@c-ware.de>
Sent: Monday, April 27, 2020 1:07 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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://gitbox.apache.org/repos/asf/royale-asjs.git
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 <ah...@apache.org>
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"/>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Christofer Dutz <ch...@c-ware.de>.
Well I just had a look and it seems as if the plugin does support retrying:
https://maven.apache.org/wagon/wagon-providers/wagon-http/
So from this:
-Dmaven.wagon.http.retryHandler.requestSentEnabled=standard
-Dmaven.wagon.http.retryHandler.count=6
Should allow enabling the retry mechanism the same way the maven-deploy-plugin is doing it.
Chris
Am 28.04.20, 19:28 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:
I was unclear as to how to take advantage of that flag with Wagon. I thought deploy used wagon and not the other way around and didn't see a similar flag for Wagon.
On 4/28/20, 10:24 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I didn’t get that it was the number of tries per artifact. That could indeed be useful.
From: Christofer Dutz<ma...@c-ware.de>
Sent: Tuesday, April 28, 2020 8:04 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
Hi Yishay,
what we do in the PLC4X project (but only for SNAPSHOTS), is that on the CI server we tell it to deploy to a local directory.
sh 'mvn -U -Pdevelopment,with-sandbox,with-logstash,with-c -DaltDeploymentRepository=snapshot-repo::default::file:./local-snapshots-dir clean deploy'
We then use the wagon plugin to deploy.
sh 'mvn -f jenkins.pom -X -P deploy-snapshots wagon:upload'
The reason we're doing it that way is that we need our builds to run on a dedicated PLC4X VM which is managed by Infra because of some low-level-networking stuff we do in our tests. In order to deploy them to Nexus, we therefore have it deploy to a local directory and then have a node with credentials deploy that for us.
Well I don't know if in your countries there are internet filters ... you probably know better ... from the technical side it sounds absolutely standard.
And regarding running the deployment multiple times ... there is one huge difference though between running the entire deployment process multiple times or telling it to re-try an artifact 6 times. I would assume that if the chance to not deploy is at 1% (and I would like to claim it being a lot lower from my experience) and you have let's say 500 artifacts ... the chances are pretty slim to have the build pass as a whole. However if you don't fail the deployment if one artifact fails, but re-try every one up to 6 times, then the chances it passes are pretty high. In the end, if things would go south exactly 5 times for every artifact it would sort of be like if you tried running the bunch 6000 times.
Chris
Am 28.04.20, 18:21 schrieb "Yishay Weiss" <yi...@hotmail.com>:
Hi Chris,
I just did an upload test and it came out 4.7mbps. Download came out 538kbps. I’m uploading from Israel, my ISP is Partner Communications, I’m using a WIFI network. My latest failure was half an hour ago (18:47 GMT +3).
Thanks for pointing out the config option on the deployment plugin, though I’ve already tried more than 6 times.
I’m wondering if it’s possible to package before uploading and resume on failure. There are lots of messages of transfers of ~40 bytes. I don’t know if they’re opening a separate connection for each of these transfers but it seems inefficient and it’s evidently fragile.
Thanks,
Yishay
From: Christofer Dutz<ma...@c-ware.de>
Sent: Tuesday, April 28, 2020 4:59 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
Side-question ...
So if you were using the maven wagon plugin (no matter if the apache one or the other) and were having issues, I would like to ask at infra if they know what they are and what might be causing them.
Cause I have staged many releases on that server and never had issues (ok ... except that it took AAAAAAGES staging a PLC4X release in a plane).
Perhaps there are some infrastructural issues like web-filters etc. that could be interfering.
So could you please tell me (if you want in off-list) from which country you were staging things (perhaps the type (DSL, Cable, ...) ... how many Mbit bandwith and name of your internet-provider).
Also the time you had problems could be important (perhaps we can see something in the logs).
And did you see the config option I added to the deploy plugin?
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.8.2</version>
<!-- If deploying fails due to repo or network problems, retry the given number of times (1-10) -->
<configuration>
<retryFailedDeploymentCount>6</retryFailedDeploymentCount>
</configuration>
</plugin>
Perhaps that could help?
Chris
Am 28.04.20, 10:57 schrieb "Yishay Weiss" <yi...@hotmail.com>:
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<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 9:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <ah...@adobe.com.INVALID> 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%7C6cd664bf1d564df9077d08d7eb990f27%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236914935820254&sdata=q5HTwadLsXvf5v4nIF3lri5A6p0kejL9Dd%2FhBI38mSA%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%7C6cd664bf1d564df9077d08d7eb990f27%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236914935820254&sdata=q5HTwadLsXvf5v4nIF3lri5A6p0kejL9Dd%2FhBI38mSA%3D&reserved=0</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7C6cd664bf1d564df9077d08d7eb990f27%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236914935820254&sdata=WQaS%2FITTZRVgANXjC54Vw00wRqZoNUFlzp4IJ%2F6kUhw%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 <ah...@apache.org>
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"/>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I was unclear as to how to take advantage of that flag with Wagon. I thought deploy used wagon and not the other way around and didn't see a similar flag for Wagon.
On 4/28/20, 10:24 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
I didn’t get that it was the number of tries per artifact. That could indeed be useful.
From: Christofer Dutz<ma...@c-ware.de>
Sent: Tuesday, April 28, 2020 8:04 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
Hi Yishay,
what we do in the PLC4X project (but only for SNAPSHOTS), is that on the CI server we tell it to deploy to a local directory.
sh 'mvn -U -Pdevelopment,with-sandbox,with-logstash,with-c -DaltDeploymentRepository=snapshot-repo::default::file:./local-snapshots-dir clean deploy'
We then use the wagon plugin to deploy.
sh 'mvn -f jenkins.pom -X -P deploy-snapshots wagon:upload'
The reason we're doing it that way is that we need our builds to run on a dedicated PLC4X VM which is managed by Infra because of some low-level-networking stuff we do in our tests. In order to deploy them to Nexus, we therefore have it deploy to a local directory and then have a node with credentials deploy that for us.
Well I don't know if in your countries there are internet filters ... you probably know better ... from the technical side it sounds absolutely standard.
And regarding running the deployment multiple times ... there is one huge difference though between running the entire deployment process multiple times or telling it to re-try an artifact 6 times. I would assume that if the chance to not deploy is at 1% (and I would like to claim it being a lot lower from my experience) and you have let's say 500 artifacts ... the chances are pretty slim to have the build pass as a whole. However if you don't fail the deployment if one artifact fails, but re-try every one up to 6 times, then the chances it passes are pretty high. In the end, if things would go south exactly 5 times for every artifact it would sort of be like if you tried running the bunch 6000 times.
Chris
Am 28.04.20, 18:21 schrieb "Yishay Weiss" <yi...@hotmail.com>:
Hi Chris,
I just did an upload test and it came out 4.7mbps. Download came out 538kbps. I’m uploading from Israel, my ISP is Partner Communications, I’m using a WIFI network. My latest failure was half an hour ago (18:47 GMT +3).
Thanks for pointing out the config option on the deployment plugin, though I’ve already tried more than 6 times.
I’m wondering if it’s possible to package before uploading and resume on failure. There are lots of messages of transfers of ~40 bytes. I don’t know if they’re opening a separate connection for each of these transfers but it seems inefficient and it’s evidently fragile.
Thanks,
Yishay
From: Christofer Dutz<ma...@c-ware.de>
Sent: Tuesday, April 28, 2020 4:59 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
Side-question ...
So if you were using the maven wagon plugin (no matter if the apache one or the other) and were having issues, I would like to ask at infra if they know what they are and what might be causing them.
Cause I have staged many releases on that server and never had issues (ok ... except that it took AAAAAAGES staging a PLC4X release in a plane).
Perhaps there are some infrastructural issues like web-filters etc. that could be interfering.
So could you please tell me (if you want in off-list) from which country you were staging things (perhaps the type (DSL, Cable, ...) ... how many Mbit bandwith and name of your internet-provider).
Also the time you had problems could be important (perhaps we can see something in the logs).
And did you see the config option I added to the deploy plugin?
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.8.2</version>
<!-- If deploying fails due to repo or network problems, retry the given number of times (1-10) -->
<configuration>
<retryFailedDeploymentCount>6</retryFailedDeploymentCount>
</configuration>
</plugin>
Perhaps that could help?
Chris
Am 28.04.20, 10:57 schrieb "Yishay Weiss" <yi...@hotmail.com>:
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<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 9:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <ah...@adobe.com.INVALID> 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%7C6cd664bf1d564df9077d08d7eb990f27%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236914935820254&sdata=q5HTwadLsXvf5v4nIF3lri5A6p0kejL9Dd%2FhBI38mSA%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%7C6cd664bf1d564df9077d08d7eb990f27%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236914935820254&sdata=q5HTwadLsXvf5v4nIF3lri5A6p0kejL9Dd%2FhBI38mSA%3D&reserved=0</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7C6cd664bf1d564df9077d08d7eb990f27%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236914935820254&sdata=WQaS%2FITTZRVgANXjC54Vw00wRqZoNUFlzp4IJ%2F6kUhw%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 <ah...@apache.org>
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"/>
RE: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Yishay Weiss <yi...@hotmail.com>.
I didn’t get that it was the number of tries per artifact. That could indeed be useful.
From: Christofer Dutz<ma...@c-ware.de>
Sent: Tuesday, April 28, 2020 8:04 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
Hi Yishay,
what we do in the PLC4X project (but only for SNAPSHOTS), is that on the CI server we tell it to deploy to a local directory.
sh 'mvn -U -Pdevelopment,with-sandbox,with-logstash,with-c -DaltDeploymentRepository=snapshot-repo::default::file:./local-snapshots-dir clean deploy'
We then use the wagon plugin to deploy.
sh 'mvn -f jenkins.pom -X -P deploy-snapshots wagon:upload'
The reason we're doing it that way is that we need our builds to run on a dedicated PLC4X VM which is managed by Infra because of some low-level-networking stuff we do in our tests. In order to deploy them to Nexus, we therefore have it deploy to a local directory and then have a node with credentials deploy that for us.
Well I don't know if in your countries there are internet filters ... you probably know better ... from the technical side it sounds absolutely standard.
And regarding running the deployment multiple times ... there is one huge difference though between running the entire deployment process multiple times or telling it to re-try an artifact 6 times. I would assume that if the chance to not deploy is at 1% (and I would like to claim it being a lot lower from my experience) and you have let's say 500 artifacts ... the chances are pretty slim to have the build pass as a whole. However if you don't fail the deployment if one artifact fails, but re-try every one up to 6 times, then the chances it passes are pretty high. In the end, if things would go south exactly 5 times for every artifact it would sort of be like if you tried running the bunch 6000 times.
Chris
Am 28.04.20, 18:21 schrieb "Yishay Weiss" <yi...@hotmail.com>:
Hi Chris,
I just did an upload test and it came out 4.7mbps. Download came out 538kbps. I’m uploading from Israel, my ISP is Partner Communications, I’m using a WIFI network. My latest failure was half an hour ago (18:47 GMT +3).
Thanks for pointing out the config option on the deployment plugin, though I’ve already tried more than 6 times.
I’m wondering if it’s possible to package before uploading and resume on failure. There are lots of messages of transfers of ~40 bytes. I don’t know if they’re opening a separate connection for each of these transfers but it seems inefficient and it’s evidently fragile.
Thanks,
Yishay
From: Christofer Dutz<ma...@c-ware.de>
Sent: Tuesday, April 28, 2020 4:59 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
Side-question ...
So if you were using the maven wagon plugin (no matter if the apache one or the other) and were having issues, I would like to ask at infra if they know what they are and what might be causing them.
Cause I have staged many releases on that server and never had issues (ok ... except that it took AAAAAAGES staging a PLC4X release in a plane).
Perhaps there are some infrastructural issues like web-filters etc. that could be interfering.
So could you please tell me (if you want in off-list) from which country you were staging things (perhaps the type (DSL, Cable, ...) ... how many Mbit bandwith and name of your internet-provider).
Also the time you had problems could be important (perhaps we can see something in the logs).
And did you see the config option I added to the deploy plugin?
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.8.2</version>
<!-- If deploying fails due to repo or network problems, retry the given number of times (1-10) -->
<configuration>
<retryFailedDeploymentCount>6</retryFailedDeploymentCount>
</configuration>
</plugin>
Perhaps that could help?
Chris
Am 28.04.20, 10:57 schrieb "Yishay Weiss" <yi...@hotmail.com>:
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<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 9:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <ah...@adobe.com.INVALID> 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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=IoyjqPDfnGwx6lT%2FInX0kxVedeg14iHR7SOlcSbvz0w%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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=IoyjqPDfnGwx6lT%2FInX0kxVedeg14iHR7SOlcSbvz0w%3D&reserved=0</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=4xo1SKufZ0YC5A%2FMmL7krg%2BQcE%2BNBQ9W286q4zioDdw%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 <ah...@apache.org>
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"/>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Yishay,
what we do in the PLC4X project (but only for SNAPSHOTS), is that on the CI server we tell it to deploy to a local directory.
sh 'mvn -U -Pdevelopment,with-sandbox,with-logstash,with-c -DaltDeploymentRepository=snapshot-repo::default::file:./local-snapshots-dir clean deploy'
We then use the wagon plugin to deploy.
sh 'mvn -f jenkins.pom -X -P deploy-snapshots wagon:upload'
The reason we're doing it that way is that we need our builds to run on a dedicated PLC4X VM which is managed by Infra because of some low-level-networking stuff we do in our tests. In order to deploy them to Nexus, we therefore have it deploy to a local directory and then have a node with credentials deploy that for us.
Well I don't know if in your countries there are internet filters ... you probably know better ... from the technical side it sounds absolutely standard.
And regarding running the deployment multiple times ... there is one huge difference though between running the entire deployment process multiple times or telling it to re-try an artifact 6 times. I would assume that if the chance to not deploy is at 1% (and I would like to claim it being a lot lower from my experience) and you have let's say 500 artifacts ... the chances are pretty slim to have the build pass as a whole. However if you don't fail the deployment if one artifact fails, but re-try every one up to 6 times, then the chances it passes are pretty high. In the end, if things would go south exactly 5 times for every artifact it would sort of be like if you tried running the bunch 6000 times.
Chris
Am 28.04.20, 18:21 schrieb "Yishay Weiss" <yi...@hotmail.com>:
Hi Chris,
I just did an upload test and it came out 4.7mbps. Download came out 538kbps. I’m uploading from Israel, my ISP is Partner Communications, I’m using a WIFI network. My latest failure was half an hour ago (18:47 GMT +3).
Thanks for pointing out the config option on the deployment plugin, though I’ve already tried more than 6 times.
I’m wondering if it’s possible to package before uploading and resume on failure. There are lots of messages of transfers of ~40 bytes. I don’t know if they’re opening a separate connection for each of these transfers but it seems inefficient and it’s evidently fragile.
Thanks,
Yishay
From: Christofer Dutz<ma...@c-ware.de>
Sent: Tuesday, April 28, 2020 4:59 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
Side-question ...
So if you were using the maven wagon plugin (no matter if the apache one or the other) and were having issues, I would like to ask at infra if they know what they are and what might be causing them.
Cause I have staged many releases on that server and never had issues (ok ... except that it took AAAAAAGES staging a PLC4X release in a plane).
Perhaps there are some infrastructural issues like web-filters etc. that could be interfering.
So could you please tell me (if you want in off-list) from which country you were staging things (perhaps the type (DSL, Cable, ...) ... how many Mbit bandwith and name of your internet-provider).
Also the time you had problems could be important (perhaps we can see something in the logs).
And did you see the config option I added to the deploy plugin?
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.8.2</version>
<!-- If deploying fails due to repo or network problems, retry the given number of times (1-10) -->
<configuration>
<retryFailedDeploymentCount>6</retryFailedDeploymentCount>
</configuration>
</plugin>
Perhaps that could help?
Chris
Am 28.04.20, 10:57 schrieb "Yishay Weiss" <yi...@hotmail.com>:
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<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 9:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <ah...@adobe.com.INVALID> 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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=IoyjqPDfnGwx6lT%2FInX0kxVedeg14iHR7SOlcSbvz0w%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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=IoyjqPDfnGwx6lT%2FInX0kxVedeg14iHR7SOlcSbvz0w%3D&reserved=0</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=4xo1SKufZ0YC5A%2FMmL7krg%2BQcE%2BNBQ9W286q4zioDdw%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 <ah...@apache.org>
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"/>
RE: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Yishay Weiss <yi...@hotmail.com>.
Hi Chris,
I just did an upload test and it came out 4.7mbps. Download came out 538kbps. I’m uploading from Israel, my ISP is Partner Communications, I’m using a WIFI network. My latest failure was half an hour ago (18:47 GMT +3).
Thanks for pointing out the config option on the deployment plugin, though I’ve already tried more than 6 times.
I’m wondering if it’s possible to package before uploading and resume on failure. There are lots of messages of transfers of ~40 bytes. I don’t know if they’re opening a separate connection for each of these transfers but it seems inefficient and it’s evidently fragile.
Thanks,
Yishay
From: Christofer Dutz<ma...@c-ware.de>
Sent: Tuesday, April 28, 2020 4:59 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
Side-question ...
So if you were using the maven wagon plugin (no matter if the apache one or the other) and were having issues, I would like to ask at infra if they know what they are and what might be causing them.
Cause I have staged many releases on that server and never had issues (ok ... except that it took AAAAAAGES staging a PLC4X release in a plane).
Perhaps there are some infrastructural issues like web-filters etc. that could be interfering.
So could you please tell me (if you want in off-list) from which country you were staging things (perhaps the type (DSL, Cable, ...) ... how many Mbit bandwith and name of your internet-provider).
Also the time you had problems could be important (perhaps we can see something in the logs).
And did you see the config option I added to the deploy plugin?
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.8.2</version>
<!-- If deploying fails due to repo or network problems, retry the given number of times (1-10) -->
<configuration>
<retryFailedDeploymentCount>6</retryFailedDeploymentCount>
</configuration>
</plugin>
Perhaps that could help?
Chris
Am 28.04.20, 10:57 schrieb "Yishay Weiss" <yi...@hotmail.com>:
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<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 9:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <ah...@adobe.com.INVALID> 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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=IoyjqPDfnGwx6lT%2FInX0kxVedeg14iHR7SOlcSbvz0w%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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=IoyjqPDfnGwx6lT%2FInX0kxVedeg14iHR7SOlcSbvz0w%3D&reserved=0</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=4xo1SKufZ0YC5A%2FMmL7krg%2BQcE%2BNBQ9W286q4zioDdw%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 <ah...@apache.org>
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"/>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Chris,
I had that issue, so my data may also could be relevant.
Poland, I was using WiFi router which I have in my house - it's cable
connection. Speed is 30MB Download/Upload.
Thanks,
Piotr
wt., 28 kwi 2020 o 15:59 Christofer Dutz <ch...@c-ware.de>
napisał(a):
> Side-question ...
>
> So if you were using the maven wagon plugin (no matter if the apache one
> or the other) and were having issues, I would like to ask at infra if they
> know what they are and what might be causing them.
>
> Cause I have staged many releases on that server and never had issues (ok
> ... except that it took AAAAAAGES staging a PLC4X release in a plane).
>
> Perhaps there are some infrastructural issues like web-filters etc. that
> could be interfering.
>
> So could you please tell me (if you want in off-list) from which country
> you were staging things (perhaps the type (DSL, Cable, ...) ... how many
> Mbit bandwith and name of your internet-provider).
>
> Also the time you had problems could be important (perhaps we can see
> something in the logs).
>
> And did you see the config option I added to the deploy plugin?
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-deploy-plugin</artifactId>
> <version>2.8.2</version>
> <!-- If deploying fails due to repo or network problems, retry
> the given number of times (1-10) -->
> <configuration>
> <retryFailedDeploymentCount>6</retryFailedDeploymentCount>
> </configuration>
> </plugin>
>
> Perhaps that could help?
>
> Chris
>
>
>
> Am 28.04.20, 10:57 schrieb "Yishay Weiss" <yi...@hotmail.com>:
>
> 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<ma...@adobe.com.INVALID>
> Sent: Tuesday, April 28, 2020 9:29 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> 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" <ah...@adobe.com.INVALID> 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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=IoyjqPDfnGwx6lT%2FInX0kxVedeg14iHR7SOlcSbvz0w%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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=IoyjqPDfnGwx6lT%2FInX0kxVedeg14iHR7SOlcSbvz0w%3D&reserved=0
> </url>
> </configuration>
> </plugin>
>
> HTH,
> -Alex
>
> On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID>
> 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" <
> christofer.dutz@c-ware.de> 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" <
> yishayjobs@hotmail.com>:
>
> Awesome
>
> ________________________________
> From: aharui@apache.org <ah...@apache.org>
> Sent: Monday, April 27, 2020 8:56:00 AM
> To: commits@royale.apache.org <
> commits@royale.apache.org>
> 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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=4xo1SKufZ0YC5A%2FMmL7krg%2BQcE%2BNBQ9W286q4zioDdw%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 <ah...@apache.org>
> 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"/>
>
>
>
>
>
>
>
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Christofer Dutz <ch...@c-ware.de>.
Side-question ...
So if you were using the maven wagon plugin (no matter if the apache one or the other) and were having issues, I would like to ask at infra if they know what they are and what might be causing them.
Cause I have staged many releases on that server and never had issues (ok ... except that it took AAAAAAGES staging a PLC4X release in a plane).
Perhaps there are some infrastructural issues like web-filters etc. that could be interfering.
So could you please tell me (if you want in off-list) from which country you were staging things (perhaps the type (DSL, Cable, ...) ... how many Mbit bandwith and name of your internet-provider).
Also the time you had problems could be important (perhaps we can see something in the logs).
And did you see the config option I added to the deploy plugin?
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.8.2</version>
<!-- If deploying fails due to repo or network problems, retry the given number of times (1-10) -->
<configuration>
<retryFailedDeploymentCount>6</retryFailedDeploymentCount>
</configuration>
</plugin>
Perhaps that could help?
Chris
Am 28.04.20, 10:57 schrieb "Yishay Weiss" <yi...@hotmail.com>:
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<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 9:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <ah...@adobe.com.INVALID> 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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=IoyjqPDfnGwx6lT%2FInX0kxVedeg14iHR7SOlcSbvz0w%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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=IoyjqPDfnGwx6lT%2FInX0kxVedeg14iHR7SOlcSbvz0w%3D&reserved=0</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=4xo1SKufZ0YC5A%2FMmL7krg%2BQcE%2BNBQ9W286q4zioDdw%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 <ah...@apache.org>
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"/>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Alex Harui <ah...@adobe.com.INVALID>.
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" <yi...@hotmail.com> 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<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 7:46 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 9:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <ah...@adobe.com.INVALID> 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" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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 <ah...@apache.org>
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"/>
RE: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Yishay Weiss <yi...@hotmail.com>.
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<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 7:46 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <yi...@hotmail.com> 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<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 9:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <ah...@adobe.com.INVALID> 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%7C00a9ac7acc8d4cc8389a08d7eb522a1d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236610438817056&sdata=n5ibNo6KRu6TGPGW8UTz%2BeJ8sIEdRgu982RhbWpAyIY%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%7C00a9ac7acc8d4cc8389a08d7eb522a1d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236610438817056&sdata=n5ibNo6KRu6TGPGW8UTz%2BeJ8sIEdRgu982RhbWpAyIY%3D&reserved=0</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7C00a9ac7acc8d4cc8389a08d7eb522a1d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236610438817056&sdata=tguaj%2BsH26zluSdyu3oJpEkR0jjoOC1BOF05BOOptr4%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 <ah...@apache.org>
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"/>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Alex Harui <ah...@adobe.com.INVALID>.
FWIW, the only time I had upload issues to staging was using my Windows computer while I was streaming video on my Roku TV (both on Wifi). Don't know if you have access to a Windows computer, Chris, but if you have one and make the network busy maybe you can reproduce it.
-Alex
On 4/29/20, 11:19 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
Well It's difficult to track down a problem I can't reproduce.
If I could, it would be easy.
I would probably run WireShark in parallel and record the traffic and check what's going wrong.
If you want, Yishay, you could create a recording and somehow send that to me, I could try and have a look ... but I would imagine the file to be "lengthy" .. and ideals don't run any video or audio streamings while recording (Believe me ... I've done several PLC communication recordings while running some 4k festival streams in the background ... that's no fun)
Did the changes I submitted change anything?
You should be able to profit from them without having to re-release.
Chris
Am 29.04.20, 17:51 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:
Chris, we've had this problem for years. Nobody is stopping you from figuring it out. I don't have the skills to do further analysis and we use the configuration you recommend that works for you and I. I think it is a bug in Maven/Wagon/StagingServer/Networking so I am proposing workarounds instead of putting people down.
The problem uploading to staging seem to happen mainly to Windows users. IIRC, Piotr switched to a Mac using the same wires in his home and it got better. But I've used Windows out of my house near Seattle and it worked, and I'm interested to see if the CI server somewhere in the US also works.
Also, there is some evidence that the upload will happen much faster from the CI server than from Yishay's home, so it could be a potential timesaver to upload from the CI server. To me and hopefully others, not requiring Macs and not hogging your local computer and network bandwidth are useful improvements.
-Alex
On 4/29/20, 2:14 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
Oh gee ...
ok ... so instead of trying to find out what the problem is,
you're adding a bunch of additional steps to the already extremely lengthy list?
I mean it's not that the internet and especially the maven infrastructure hates you guys and therefore discriminates you.
I would assume that probably the problem is somehow related to your (maven) setup.
Am I correct with the assumption, that the RMs that have had these issues aren't very frequent users of Maven otherwise?
I mean ... I ran the steps up to typedefs and all deployment was working fine without any issues, so I could assume that there might be an issue with your general setup.
Chris
Am 29.04.20, 09:38 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:
I would first try #1. Hopefully you can have a good enough connection to upload a bunch of small .asc files.
If we have to go with #2, I think there are lots of possibilities.
a) have the Ant script zip up all of the .asc files
b) create a git repo where you push the .asc files
c) figure out how to use dropbox or something like that.
HTH,
-Alex
PS: I'm shutting down for tonight.
On 4/29/20, 12:26 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>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.
How do you suggest doing (2)? As I see it, we would need some SCP connection configured, or lots of manual steps with RDP. What am I missing?
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Christofer Dutz <ch...@c-ware.de>.
Well It's difficult to track down a problem I can't reproduce.
If I could, it would be easy.
I would probably run WireShark in parallel and record the traffic and check what's going wrong.
If you want, Yishay, you could create a recording and somehow send that to me, I could try and have a look ... but I would imagine the file to be "lengthy" .. and ideals don't run any video or audio streamings while recording (Believe me ... I've done several PLC communication recordings while running some 4k festival streams in the background ... that's no fun)
Did the changes I submitted change anything?
You should be able to profit from them without having to re-release.
Chris
Am 29.04.20, 17:51 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:
Chris, we've had this problem for years. Nobody is stopping you from figuring it out. I don't have the skills to do further analysis and we use the configuration you recommend that works for you and I. I think it is a bug in Maven/Wagon/StagingServer/Networking so I am proposing workarounds instead of putting people down.
The problem uploading to staging seem to happen mainly to Windows users. IIRC, Piotr switched to a Mac using the same wires in his home and it got better. But I've used Windows out of my house near Seattle and it worked, and I'm interested to see if the CI server somewhere in the US also works.
Also, there is some evidence that the upload will happen much faster from the CI server than from Yishay's home, so it could be a potential timesaver to upload from the CI server. To me and hopefully others, not requiring Macs and not hogging your local computer and network bandwidth are useful improvements.
-Alex
On 4/29/20, 2:14 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
Oh gee ...
ok ... so instead of trying to find out what the problem is,
you're adding a bunch of additional steps to the already extremely lengthy list?
I mean it's not that the internet and especially the maven infrastructure hates you guys and therefore discriminates you.
I would assume that probably the problem is somehow related to your (maven) setup.
Am I correct with the assumption, that the RMs that have had these issues aren't very frequent users of Maven otherwise?
I mean ... I ran the steps up to typedefs and all deployment was working fine without any issues, so I could assume that there might be an issue with your general setup.
Chris
Am 29.04.20, 09:38 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:
I would first try #1. Hopefully you can have a good enough connection to upload a bunch of small .asc files.
If we have to go with #2, I think there are lots of possibilities.
a) have the Ant script zip up all of the .asc files
b) create a git repo where you push the .asc files
c) figure out how to use dropbox or something like that.
HTH,
-Alex
PS: I'm shutting down for tonight.
On 4/29/20, 12:26 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>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.
How do you suggest doing (2)? As I see it, we would need some SCP connection configured, or lots of manual steps with RDP. What am I missing?
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Chris, we've had this problem for years. Nobody is stopping you from figuring it out. I don't have the skills to do further analysis and we use the configuration you recommend that works for you and I. I think it is a bug in Maven/Wagon/StagingServer/Networking so I am proposing workarounds instead of putting people down.
The problem uploading to staging seem to happen mainly to Windows users. IIRC, Piotr switched to a Mac using the same wires in his home and it got better. But I've used Windows out of my house near Seattle and it worked, and I'm interested to see if the CI server somewhere in the US also works.
Also, there is some evidence that the upload will happen much faster from the CI server than from Yishay's home, so it could be a potential timesaver to upload from the CI server. To me and hopefully others, not requiring Macs and not hogging your local computer and network bandwidth are useful improvements.
-Alex
On 4/29/20, 2:14 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
Oh gee ...
ok ... so instead of trying to find out what the problem is,
you're adding a bunch of additional steps to the already extremely lengthy list?
I mean it's not that the internet and especially the maven infrastructure hates you guys and therefore discriminates you.
I would assume that probably the problem is somehow related to your (maven) setup.
Am I correct with the assumption, that the RMs that have had these issues aren't very frequent users of Maven otherwise?
I mean ... I ran the steps up to typedefs and all deployment was working fine without any issues, so I could assume that there might be an issue with your general setup.
Chris
Am 29.04.20, 09:38 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:
I would first try #1. Hopefully you can have a good enough connection to upload a bunch of small .asc files.
If we have to go with #2, I think there are lots of possibilities.
a) have the Ant script zip up all of the .asc files
b) create a git repo where you push the .asc files
c) figure out how to use dropbox or something like that.
HTH,
-Alex
PS: I'm shutting down for tonight.
On 4/29/20, 12:26 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>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.
How do you suggest doing (2)? As I see it, we would need some SCP connection configured, or lots of manual steps with RDP. What am I missing?
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Christofer Dutz <ch...@c-ware.de>.
Oh gee ...
ok ... so instead of trying to find out what the problem is,
you're adding a bunch of additional steps to the already extremely lengthy list?
I mean it's not that the internet and especially the maven infrastructure hates you guys and therefore discriminates you.
I would assume that probably the problem is somehow related to your (maven) setup.
Am I correct with the assumption, that the RMs that have had these issues aren't very frequent users of Maven otherwise?
I mean ... I ran the steps up to typedefs and all deployment was working fine without any issues, so I could assume that there might be an issue with your general setup.
Chris
Am 29.04.20, 09:38 schrieb "Alex Harui" <ah...@adobe.com.INVALID>:
I would first try #1. Hopefully you can have a good enough connection to upload a bunch of small .asc files.
If we have to go with #2, I think there are lots of possibilities.
a) have the Ant script zip up all of the .asc files
b) create a git repo where you push the .asc files
c) figure out how to use dropbox or something like that.
HTH,
-Alex
PS: I'm shutting down for tonight.
On 4/29/20, 12:26 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>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.
How do you suggest doing (2)? As I see it, we would need some SCP connection configured, or lots of manual steps with RDP. What am I missing?
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I would first try #1. Hopefully you can have a good enough connection to upload a bunch of small .asc files.
If we have to go with #2, I think there are lots of possibilities.
a) have the Ant script zip up all of the .asc files
b) create a git repo where you push the .asc files
c) figure out how to use dropbox or something like that.
HTH,
-Alex
PS: I'm shutting down for tonight.
On 4/29/20, 12:26 AM, "Yishay Weiss" <yi...@hotmail.com> wrote:
>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.
How do you suggest doing (2)? As I see it, we would need some SCP connection configured, or lots of manual steps with RDP. What am I missing?
RE: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Yishay Weiss <yi...@hotmail.com>.
>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.
How do you suggest doing (2)? As I see it, we would need some SCP connection configured, or lots of manual steps with RDP. What am I missing?
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Alex Harui <ah...@adobe.com.INVALID>.
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" <yi...@hotmail.com> 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<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 9:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <ah...@adobe.com.INVALID> 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%7C00a9ac7acc8d4cc8389a08d7eb522a1d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236610438817056&sdata=n5ibNo6KRu6TGPGW8UTz%2BeJ8sIEdRgu982RhbWpAyIY%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%7C00a9ac7acc8d4cc8389a08d7eb522a1d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236610438817056&sdata=n5ibNo6KRu6TGPGW8UTz%2BeJ8sIEdRgu982RhbWpAyIY%3D&reserved=0</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7C00a9ac7acc8d4cc8389a08d7eb522a1d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236610438817056&sdata=tguaj%2BsH26zluSdyu3oJpEkR0jjoOC1BOF05BOOptr4%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 <ah...@apache.org>
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"/>
RE: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Yishay Weiss <yi...@hotmail.com>.
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<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 9:29 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
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" <ah...@adobe.com.INVALID> 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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=IoyjqPDfnGwx6lT%2FInX0kxVedeg14iHR7SOlcSbvz0w%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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=IoyjqPDfnGwx6lT%2FInX0kxVedeg14iHR7SOlcSbvz0w%3D&reserved=0</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=4xo1SKufZ0YC5A%2FMmL7krg%2BQcE%2BNBQ9W286q4zioDdw%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 <ah...@apache.org>
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"/>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Alex Harui <ah...@adobe.com.INVALID>.
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" <ah...@adobe.com.INVALID> 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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=IoyjqPDfnGwx6lT%2FInX0kxVedeg14iHR7SOlcSbvz0w%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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=IoyjqPDfnGwx6lT%2FInX0kxVedeg14iHR7SOlcSbvz0w%3D&reserved=0</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7Ca9bc7faa5625462a70a008d7eb326130%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236473922869895&sdata=4xo1SKufZ0YC5A%2FMmL7krg%2BQcE%2BNBQ9W286q4zioDdw%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 <ah...@apache.org>
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"/>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Alex Harui <ah...@adobe.com.INVALID>.
We are using org.codehaus.mojo.wagon 2.0.0. Is there a newer one?
Looking at that pom, we might be able to upgrade its wagon plugins by adding -Dwagon.api.version=3.4.0 to the command line.
It might be a better use of time to try to get the upload to run from the CI server.
-Alex
On 4/28/20, 11:47 PM, "Christofer Dutz" <ch...@c-ware.de> wrote:
Apache Wagon is the provider .... not the plugin.
I think you might need to use the newest version of the wagon-maven-plugin and replace the wagon provider by excluding the old and adding a dependency to the new.
The thing is that wagon is actually the logic used internally by all sorts of maven subsystems. It's used for dependency download and upload, version detections etc. The wagon-maven-plugin is just a small wrapper plugin around the wagon core to allow to do some of the stuff using the API directly.
And regarding Infra ... no problems were known to them with regards to service outages or extended unresponsiveness.
Chris
Am 29.04.20, 08:24 schrieb "Yishay Weiss" <yi...@hotmail.com>:
I read that retry was only implemented in wagon 3.4.0 and up. So I replaced the pom.xml entry according to Alex’s suggestion but I’m getting
[exec] [DEBUG] Resolving plugin prefix wagon from [org.apache.maven.plugins, org.codehaus.mojo]
[exec] [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.wagon:wagon:3.4.0: Plugin org.apache.maven.wagon:wagon:3.4.0 or one of its dependencies could not be resolved: Failure to find org.apache.maven.wagon:wagon:jar:3.4.0 in https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepo.maven.apache.org%2Fmaven2&data=02%7C01%7Caharui%40adobe.com%7Cb703c63548a440486dfb08d7ec092066%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637237396255828787&sdata=DMXCn%2Bf4P%2BO2UKmUH5aBd1UmK6ipNeCM2rxZ730FdQU%3D&reserved=0 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
[exec] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.wagon:wagon:3.4.0 or one of its dependencies could not be resolved: Failure to find org.apache.maven.wagon:wagon:jar:3.4.0 in https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepo.maven.apache.org%2Fmaven2&data=02%7C01%7Caharui%40adobe.com%7Cb703c63548a440486dfb08d7ec092066%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637237396255828787&sdata=DMXCn%2Bf4P%2BO2UKmUH5aBd1UmK6ipNeCM2rxZ730FdQU%3D&reserved=0 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 8:09 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
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%7Cb703c63548a440486dfb08d7ec092066%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637237396255828787&sdata=cn3NaVbC1ciFWG816GFvky0cmUL0VatGNi5hy2sB6JY%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%7Cb703c63548a440486dfb08d7ec092066%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637237396255828787&sdata=cn3NaVbC1ciFWG816GFvky0cmUL0VatGNi5hy2sB6JY%3D&reserved=0</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7Cb703c63548a440486dfb08d7ec092066%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637237396255828787&sdata=e6PhAhwBJhZvoMzzNd3030maMIVOUkegGvMyOeMZlPE%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 <ah...@apache.org>
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"/>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Christofer Dutz <ch...@c-ware.de>.
Ok ... there you go ... haven't tested it though ....
I created a PR for each repo ... be sure that you enable the "_releasesteps-upload-release-to-staging" profile or it will probably not pick up the config.
Chris
Am 29.04.20, 17:00 schrieb "Christofer Dutz" <ch...@c-ware.de>:
I'll whip up a PR.
Chris
Am 29.04.20, 15:24 schrieb "Yishay Weiss" <yi...@hotmail.com>:
Can you guide us through upgrading to 3.4.0?
From: Christofer Dutz<ma...@c-ware.de>
Sent: Wednesday, April 29, 2020 9:47 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
Apache Wagon is the provider .... not the plugin.
I think you might need to use the newest version of the wagon-maven-plugin and replace the wagon provider by excluding the old and adding a dependency to the new.
The thing is that wagon is actually the logic used internally by all sorts of maven subsystems. It's used for dependency download and upload, version detections etc. The wagon-maven-plugin is just a small wrapper plugin around the wagon core to allow to do some of the stuff using the API directly.
And regarding Infra ... no problems were known to them with regards to service outages or extended unresponsiveness.
Chris
Am 29.04.20, 08:24 schrieb "Yishay Weiss" <yi...@hotmail.com>:
I read that retry was only implemented in wagon 3.4.0 and up. So I replaced the pom.xml entry according to Alex’s suggestion but I’m getting
[exec] [DEBUG] Resolving plugin prefix wagon from [org.apache.maven.plugins, org.codehaus.mojo]
[exec] [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.wagon:wagon:3.4.0: Plugin org.apache.maven.wagon:wagon:3.4.0 or one of its dependencies could not be resolved: Failure to find org.apache.maven.wagon:wagon:jar:3.4.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
[exec] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.wagon:wagon:3.4.0 or one of its dependencies could not be resolved: Failure to find org.apache.maven.wagon:wagon:jar:3.4.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 8:09 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
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://repository.apache.org/service/local/staging/deploy/maven2</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://repository.apache.org/service/local/staging/deploy/maven2</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7Cf93a7122d006493a7cf808d7eaec147b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236172044662963&sdata=uG%2FjLtaz1c%2BTaDvApclw%2Bihx5sXhm1QxQBoU91otykM%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 <ah...@apache.org>
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"/>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Christofer Dutz <ch...@c-ware.de>.
I'll whip up a PR.
Chris
Am 29.04.20, 15:24 schrieb "Yishay Weiss" <yi...@hotmail.com>:
Can you guide us through upgrading to 3.4.0?
From: Christofer Dutz<ma...@c-ware.de>
Sent: Wednesday, April 29, 2020 9:47 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
Apache Wagon is the provider .... not the plugin.
I think you might need to use the newest version of the wagon-maven-plugin and replace the wagon provider by excluding the old and adding a dependency to the new.
The thing is that wagon is actually the logic used internally by all sorts of maven subsystems. It's used for dependency download and upload, version detections etc. The wagon-maven-plugin is just a small wrapper plugin around the wagon core to allow to do some of the stuff using the API directly.
And regarding Infra ... no problems were known to them with regards to service outages or extended unresponsiveness.
Chris
Am 29.04.20, 08:24 schrieb "Yishay Weiss" <yi...@hotmail.com>:
I read that retry was only implemented in wagon 3.4.0 and up. So I replaced the pom.xml entry according to Alex’s suggestion but I’m getting
[exec] [DEBUG] Resolving plugin prefix wagon from [org.apache.maven.plugins, org.codehaus.mojo]
[exec] [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.wagon:wagon:3.4.0: Plugin org.apache.maven.wagon:wagon:3.4.0 or one of its dependencies could not be resolved: Failure to find org.apache.maven.wagon:wagon:jar:3.4.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
[exec] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.wagon:wagon:3.4.0 or one of its dependencies could not be resolved: Failure to find org.apache.maven.wagon:wagon:jar:3.4.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 8:09 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
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://repository.apache.org/service/local/staging/deploy/maven2</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://repository.apache.org/service/local/staging/deploy/maven2</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7Cf93a7122d006493a7cf808d7eaec147b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236172044662963&sdata=uG%2FjLtaz1c%2BTaDvApclw%2Bihx5sXhm1QxQBoU91otykM%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 <ah...@apache.org>
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"/>
RE: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Yishay Weiss <yi...@hotmail.com>.
Can you guide us through upgrading to 3.4.0?
From: Christofer Dutz<ma...@c-ware.de>
Sent: Wednesday, April 29, 2020 9:47 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
Apache Wagon is the provider .... not the plugin.
I think you might need to use the newest version of the wagon-maven-plugin and replace the wagon provider by excluding the old and adding a dependency to the new.
The thing is that wagon is actually the logic used internally by all sorts of maven subsystems. It's used for dependency download and upload, version detections etc. The wagon-maven-plugin is just a small wrapper plugin around the wagon core to allow to do some of the stuff using the API directly.
And regarding Infra ... no problems were known to them with regards to service outages or extended unresponsiveness.
Chris
Am 29.04.20, 08:24 schrieb "Yishay Weiss" <yi...@hotmail.com>:
I read that retry was only implemented in wagon 3.4.0 and up. So I replaced the pom.xml entry according to Alex’s suggestion but I’m getting
[exec] [DEBUG] Resolving plugin prefix wagon from [org.apache.maven.plugins, org.codehaus.mojo]
[exec] [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.wagon:wagon:3.4.0: Plugin org.apache.maven.wagon:wagon:3.4.0 or one of its dependencies could not be resolved: Failure to find org.apache.maven.wagon:wagon:jar:3.4.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
[exec] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.wagon:wagon:3.4.0 or one of its dependencies could not be resolved: Failure to find org.apache.maven.wagon:wagon:jar:3.4.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 8:09 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
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://repository.apache.org/service/local/staging/deploy/maven2</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://repository.apache.org/service/local/staging/deploy/maven2</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7Cf93a7122d006493a7cf808d7eaec147b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236172044662963&sdata=uG%2FjLtaz1c%2BTaDvApclw%2Bihx5sXhm1QxQBoU91otykM%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 <ah...@apache.org>
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"/>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Christofer Dutz <ch...@c-ware.de>.
Apache Wagon is the provider .... not the plugin.
I think you might need to use the newest version of the wagon-maven-plugin and replace the wagon provider by excluding the old and adding a dependency to the new.
The thing is that wagon is actually the logic used internally by all sorts of maven subsystems. It's used for dependency download and upload, version detections etc. The wagon-maven-plugin is just a small wrapper plugin around the wagon core to allow to do some of the stuff using the API directly.
And regarding Infra ... no problems were known to them with regards to service outages or extended unresponsiveness.
Chris
Am 29.04.20, 08:24 schrieb "Yishay Weiss" <yi...@hotmail.com>:
I read that retry was only implemented in wagon 3.4.0 and up. So I replaced the pom.xml entry according to Alex’s suggestion but I’m getting
[exec] [DEBUG] Resolving plugin prefix wagon from [org.apache.maven.plugins, org.codehaus.mojo]
[exec] [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.wagon:wagon:3.4.0: Plugin org.apache.maven.wagon:wagon:3.4.0 or one of its dependencies could not be resolved: Failure to find org.apache.maven.wagon:wagon:jar:3.4.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
[exec] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.wagon:wagon:3.4.0 or one of its dependencies could not be resolved: Failure to find org.apache.maven.wagon:wagon:jar:3.4.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 8:09 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
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://repository.apache.org/service/local/staging/deploy/maven2</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://repository.apache.org/service/local/staging/deploy/maven2</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7Cf93a7122d006493a7cf808d7eaec147b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236172044662963&sdata=uG%2FjLtaz1c%2BTaDvApclw%2Bihx5sXhm1QxQBoU91otykM%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 <ah...@apache.org>
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"/>
RE: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Yishay Weiss <yi...@hotmail.com>.
I read that retry was only implemented in wagon 3.4.0 and up. So I replaced the pom.xml entry according to Alex’s suggestion but I’m getting
[exec] [DEBUG] Resolving plugin prefix wagon from [org.apache.maven.plugins, org.codehaus.mojo]
[exec] [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.wagon:wagon:3.4.0: Plugin org.apache.maven.wagon:wagon:3.4.0 or one of its dependencies could not be resolved: Failure to find org.apache.maven.wagon:wagon:jar:3.4.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
[exec] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.wagon:wagon:3.4.0 or one of its dependencies could not be resolved: Failure to find org.apache.maven.wagon:wagon:jar:3.4.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
From: Alex Harui<ma...@adobe.com.INVALID>
Sent: Tuesday, April 28, 2020 8:09 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails
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://repository.apache.org/service/local/staging/deploy/maven2</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://repository.apache.org/service/local/staging/deploy/maven2</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7Cf93a7122d006493a7cf808d7eaec147b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236172044662963&sdata=uG%2FjLtaz1c%2BTaDvApclw%2Bihx5sXhm1QxQBoU91otykM%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 <ah...@apache.org>
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"/>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Alex Harui <ah...@adobe.com.INVALID>.
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://repository.apache.org/service/local/staging/deploy/maven2</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://repository.apache.org/service/local/staging/deploy/maven2</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <ah...@adobe.com.INVALID> 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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7Cf93a7122d006493a7cf808d7eaec147b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236172044662963&sdata=uG%2FjLtaz1c%2BTaDvApclw%2Bihx5sXhm1QxQBoU91otykM%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 <ah...@apache.org>
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"/>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Alex Harui <ah...@adobe.com.INVALID>.
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" <ch...@c-ware.de> 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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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%7C6e189d3712c442c5780308d7ea92da91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637235788787726346&sdata=Hd3eRm5I5jcAsTFGmECSZttENHige0MrmxgS4HgavgY%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 <ah...@apache.org>
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"/>
Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
Posted by Christofer Dutz <ch...@c-ware.de>.
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" <yi...@hotmail.com>:
Awesome
________________________________
From: aharui@apache.org <ah...@apache.org>
Sent: Monday, April 27, 2020 8:56:00 AM
To: commits@royale.apache.org <co...@royale.apache.org>
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://gitbox.apache.org/repos/asf/royale-asjs.git
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 <ah...@apache.org>
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"/>