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.8 git push -u origin release/0.9.8 You will need your Apache/Github username and 2FA token.
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.8-rc7 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.8
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.8
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.8
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 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.8 git push -u origin release/0.9.8 You will need your Apache/Github username and 2FA token.
Royale_Release_Step_005 - Build # 21 - Failure!
Royale_Release_Step_005 - Build # 21 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005/21/ to view the results.
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.
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.8-rc7 You will need your Apache/Github username and 2FA token.
Release Step 007 Succeeded
>From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.8 -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.8 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.8 This will upload the signed artifacts to Maven Release Staging. Do not "Close" the staging repository until the other repos have been added.
Release Step 008 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands: git push git checkout release/0.9.8 git push -u origin refs/heads/release/0.9.8 You will need your Apache/Github username and 2FA token.
Release Step 009 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_009 and run the following commands: git push You will need your Apache/Github username and 2FA token.
Release Step 010 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands: git push git push origin org.apache.royale.framework-0.9.8-rc7 You will need your Apache/Github username and 2FA token.
Royale_Release_Step_011 - Build # 22 - Failure!
Royale_Release_Step_011 - Build # 22 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_011/22/ to view the results.
Release Step 011 Succeeded
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.8 -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.8 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.8 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/)
Release Step 012 Succeeded
Folder 0.9.8 already exists. Continue to next step.
Release Step 013 Succeeded
Note: before running these steps make sure that PLAYERGLOBAL_HOME is set and that you have PlayerGlobal installed under /11.7/playerglobal.swc >From the royale-asjs repo 1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.8 -Droyale.swc-date="08/27/21 9:06 -0800. " -Dplayerglobal.version=11.7 -Dflat.donot.ask=true -Drc=7 -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.8 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.8 -Drc=7 This will upload the signed artifacts to dist.apache.org.
