Release Step 007 Succeeded
>From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -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_007_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_007_Upload -Drelease.version=0.9.9 This will upload the signed artifacts to Maven Release Staging. Do not "Close" the staging repository until the other repos have been added.
Royale_Release_Step_007 - Build # 28 - Still Failing!
Royale_Release_Step_007 - Build # 28 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_007/28/ to view the results.
Royale_Release_Step_007 - Build # 27 - Failure!
Royale_Release_Step_007 - Build # 27 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_007/27/ to view the results.
Release Step 006 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands: git push git push origin org.apache.royale.typedefs-0.9.9-rc3 You will need your Apache/Github username and 2FA token.
Release Step 005 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005 and run the following commands: git push You will need your Apache/Github username and 2FA token.
Royale_Release_Step_005 - Build # 25 - Failure!
Royale_Release_Step_005 - Build # 25 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005/25/ to view the results.
Release Step 004 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands: git push git checkout release/0.9.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Royale_Release_Step_004 - Build # 39 - Failure!
Royale_Release_Step_004 - Build # 39 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/39/ to view the results.
Release Step 003 Succeeded
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.9
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_003_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_003_Upload
-Drelease.version=0.9.9
This will upload the signed artifacts to Maven Release Staging. If you are
getting 401 responses from Nexus (permission denied) please be sure to have
your apache creedentials configured in your .m2/settings.xml file.
Feel free to use this template if you haven't got a settings.xml yet:
http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd;
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
apache.releases.https
{your apache user id}
{your apache user password}
(Be sure to replace the placeholders with your actual apache committer id and
your Apache password)
If you already have a settings.xml, just be sure the "server" block containing
your credentials is added to a servers block in that file.
Do not "Close" the staging repository until the other repos have been added.
Release Step 002 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.9-rc3 You will need your Apache/Github username and 2FA token.
Royale_Release_Step_002 - Build # 70 - Still Failing!
Royale_Release_Step_002 - Build # 70 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/70/ to view the results.
Royale_Release_Step_002 - Build # 69 - Still Failing!
Royale_Release_Step_002 - Build # 69 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/69/ to view the results.
Royale_Release_Step_002 - Build # 68 - Failure!
Royale_Release_Step_002 - Build # 68 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/68/ to view the results.
Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands: git push git checkout release/0.9.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Release Step 003 Succeeded
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.9
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_003_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_003_Upload
-Drelease.version=0.9.9
This will upload the signed artifacts to Maven Release Staging. If you are
getting 401 responses from Nexus (permission denied) please be sure to have
your apache creedentials configured in your .m2/settings.xml file.
Feel free to use this template if you haven't got a settings.xml yet:
http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd;
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
apache.releases.https
{your apache user id}
{your apache user password}
(Be sure to replace the placeholders with your actual apache committer id and
your Apache password)
If you already have a settings.xml, just be sure the "server" block containing
your credentials is added to a servers block in that file.
Do not "Close" the staging repository until the other repos have been added.
Release Step 002 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.9-rc3 You will need your Apache/Github username and 2FA token.
Royale_Release_Step_002 - Build # 66 - Failure!
Royale_Release_Step_002 - Build # 66 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/66/ to view the results.
Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands: git push git checkout release/0.9.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
