Ups ... there's one "apache-release" too much in there ...
mvn clean deploy -Papache-release,with-distribution,option-with-swf
Chris
Am 30.04.20, 21:41 schrieb "Christofer Dutz" <[email protected]>:
Hi folks,
Just to try it out ... almost anyone that has setup his credentials in the
settings.xml could try to deploy asjs by running:
mvn clean deploy
-Papache-release,apache-release,with-distribution,option-with-swf
On the develop branch.
It would automatically build the same artifacts, sign them and instead of
creating a staging repo, would upload them to the SNAPSHOT repo.
Would be really interesting on if you really are having these upload
problems. And I mean anyone could test this without having to be RM.
It's just one command, nothing more and you can't even mess up anything as
the code isn't changed.
And by the way ... the releasesteps.xml does actually deploy a large
portion of the artifacts multiple times ...
The ant target uploadSWCs already deploys the entire artifact tree ...
there's no need for uploadJewelDark and uploadJewelLight
Chris
Am 30.04.20, 20:43 schrieb "Alex Harui" <[email protected]>:
Gee I hope that didn't cause that IP to be blocked by Apache. Keep
that in mind if you have trouble uploading from the CI server next time you
try. Find the IP address of the CI server and ask Infra if it got blocked.
There is a chance that Azure blocked as well. I guess I'll find out if I have
to pay Azure a huge bandwidth overage bill or not.
It does tell us something about the reliability of the connection on a
windows machine in the US vs your computer outside the US.
Anyway, I think you can test locally with the .asc files and figure out
the right params.
Good luck,
-Alex
On 4/30/20, 11:34 AM, "Yishay Weiss" <[email protected]> wrote:
I suspect this might be related to recent maven profile changes not
meshing well with the release script targets. I’ll see what I can dig up.
From: Yishay Weiss<mailto:[email protected]>
Sent: Thursday, April 30, 2020 9:32 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: wagon:upload problems
>I think it might be repeating the upload for each project.
Upload happens 67 times [1] in a loop. That explains why even on
the CI server after 5.5 hours it finally failed [2].
[1]
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fzh3rj&data=02%7C01%7Caharui%40adobe.com%7Cb885d9589cd447e688a908d7ed350fde%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637238684466700111&sdata=6GKpo8q5SN4jt8%2BKB0Sz574SH2u8AN9OTYnlzBteOiE%3D&reserved=0
[2]
[exec] [INFO] BUILD FAILURE
[exec] [INFO]
------------------------------------------------------------------------
[exec] [INFO] Total time: 05:36 h
[exec] [INFO] Finished at: 2020-04-30T18:01:58Z
[exec] [INFO]
------------------------------------------------------------------------
[exec] [ERROR] Failed to execute goal
org.codehaus.mojo:wagon-maven-plugin:2.0.0:upload (default-cli) on project
Effects: Error handling resource: Failed to transfer file http
s://repository.apache.org/service/local/staging/deploy/maven2/org/apache/royale/framework/Jewel-Light-NoFlat-Emphasized-Emerald-Theme/0.9.7/Jewel-Light-NoFlat-Emphasized-Emerald-Th
eme-0.9.7-js.swc with status code 400 -> [Help 1]
[exec] org.apache.maven.lifecycle.LifecycleExecutionException:
Failed to execute goal org.codehaus.mojo:wagon-maven-plugin:2.0.0:upload
(default-cli) on project Effects: Error
handling resource
