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 2020/04/25 04:19:33 UTC

Royale_Release_Step_013 - Build # 4 - Still Failing!

Royale_Release_Step_013 - Build # 4 - Still Failing:

Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_013/4/ to view the results.

Re: Release Step 013 Succeeded

Posted by Alex Harui <ah...@adobe.com.INVALID>.
Yes. https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes#localproperties

On 5/2/20, 10:02 PM, "Yishay Weiss" <yi...@hotmail.com> wrote:

    Are we supposed to create a local.properties file?
    
    C:\dev\flexjs\royale-asjs [release/0.9.7 = +1 ~0 -0 !]> ant -f releasesteps.xml Release_Step_013_Upload "-Drelease.version=0.9.7" "-Drc=3"
    Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
    Buildfile: C:\dev\flexjs\royale-asjs\releasesteps.xml
    
    check-name-and-svn:
    
    BUILD FAILED
    C:\dev\flexjs\royale-asjs\releasesteps.xml:1834: The my.name property is not set to the RM's name.  This property (and other properties) is often set in a local.prope
    rties file and copied into an empty folder before running this script.
    
    Total time: 0 seconds
    
    From: apacheroyaleci@gmail.com<ma...@gmail.com>
    Sent: Saturday, April 25, 2020 8:35 AM
    To: dev@royale.apache.org<ma...@royale.apache.org>
    Subject: Release Step 013 Succeeded
    
    From the royale-asjs repo
    1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.7 -Droyale.swc-date="04/24/20 09:07 -0700" -Dplayerglobal.version=11.7 -Dflat.donot.ask=true -Drc=2 -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_013_Sign -Drelease.version=0.9.7
    This will PGP sign the source and convenience binary packages
    4. Then run ant -f releasesteps.xml Release_Step_013_Upload -Drelease.version=0.9.7 -Drc=2
    This will upload the signed artifacts to dist.apache.org.

RE: Release Step 013 Succeeded

Posted by Yishay Weiss <yi...@hotmail.com>.
Are we supposed to create a local.properties file?

C:\dev\flexjs\royale-asjs [release/0.9.7 = +1 ~0 -0 !]> ant -f releasesteps.xml Release_Step_013_Upload "-Drelease.version=0.9.7" "-Drc=3"
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
Buildfile: C:\dev\flexjs\royale-asjs\releasesteps.xml

check-name-and-svn:

BUILD FAILED
C:\dev\flexjs\royale-asjs\releasesteps.xml:1834: The my.name property is not set to the RM's name.  This property (and other properties) is often set in a local.prope
rties file and copied into an empty folder before running this script.

Total time: 0 seconds

From: apacheroyaleci@gmail.com<ma...@gmail.com>
Sent: Saturday, April 25, 2020 8:35 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Release Step 013 Succeeded

From the royale-asjs repo
1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.7 -Droyale.swc-date="04/24/20 09:07 -0700" -Dplayerglobal.version=11.7 -Dflat.donot.ask=true -Drc=2 -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_013_Sign -Drelease.version=0.9.7
This will PGP sign the source and convenience binary packages
4. Then run ant -f releasesteps.xml Release_Step_013_Upload -Drelease.version=0.9.7 -Drc=2
This will upload the signed artifacts to dist.apache.org.

Release Step 013 Succeeded

Posted by ap...@gmail.com.
From the royale-asjs repo
1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.7 -Droyale.swc-date="04/24/20 09:07 -0700" -Dplayerglobal.version=11.7 -Dflat.donot.ask=true -Drc=2 -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_013_Sign -Drelease.version=0.9.7
This will PGP sign the source and convenience binary packages
4. Then run ant -f releasesteps.xml Release_Step_013_Upload -Drelease.version=0.9.7 -Drc=2
This will upload the signed artifacts to dist.apache.org.