You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by ap...@gmail.com on 2022/03/06 11:23:30 UTC
Royale_Release_Step_011 - Build # 24 - Failure!
Royale_Release_Step_011 - Build # 24 - Failure:
Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_011/24/ to view the results.
Release Step 011 Succeeded
Posted by ap...@gmail.com.
Warning: this step requires a secret key, so it should not be performed on the CI server. It's probably best to perform it on your PC.
From the royale-asjs repo:
1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.9 -DskipTests=true
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_011_Sign -Drelease.version=0.9.9
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_011_Upload -Drelease.version=0.9.9
This will upload the signed artifacts to Maven Release Staging. Verify that the compiler and typedefs artifacts are there along with the asjs artifacts, then hit the close to close the staging repo. (https://repository.apache.org/)
Re: Royale_Release_Step_011 - Build # 24 - Failure!
Posted by Greg Dove <gr...@gmail.com>.
I don't know, but I will look into it today (local time) and see if I can
figure it out.
On Mon, Mar 7, 2022 at 8:19 AM Yishay Weiss <yi...@hotmail.com> wrote:
> ASDoc is failing which is blocking the build.
>
> Greg, I have found out commit 63c94366f533bc1384401cdd6ba1f20057b4d999
> breaks the ASDoc example, specifically the following line:
>
> import mx.events.ResourceEvent; ResourceEvent;
>
> Do you (or anyone else) have a hunch why that may be?
>
> From: apacheroyaleci@gmail.com<ma...@gmail.com>
> Sent: Sunday, March 6, 2022 1:23 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Royale_Release_Step_011 - Build # 24 - Failure!
>
> Royale_Release_Step_011 - Build # 24 - Failure:
>
> Check console output at
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_011/24/
> to view the results.
>
>
RE: Royale_Release_Step_011 - Build # 24 - Failure!
Posted by Yishay Weiss <yi...@hotmail.com>.
ASDoc is failing which is blocking the build.
Greg, I have found out commit 63c94366f533bc1384401cdd6ba1f20057b4d999 breaks the ASDoc example, specifically the following line:
import mx.events.ResourceEvent; ResourceEvent;
Do you (or anyone else) have a hunch why that may be?
From: apacheroyaleci@gmail.com<ma...@gmail.com>
Sent: Sunday, March 6, 2022 1:23 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Royale_Release_Step_011 - Build # 24 - Failure!
Royale_Release_Step_011 - Build # 24 - Failure:
Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_011/24/ to view the results.