Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: new step 4.2.3 - validate RC using TC

...

4.2. Prepare RC on Teamcity

4.2.1. Run TC Main Release Build

Run [RELEASES] Apache Ignite / Main [1] Release Build for ignite-x.y or for ignite-x.y.z branch. You will need to enter version number (value if x.y.0 or x.y.z), and specify release candidate number. For testing purposes, it is recommended to use rc0. You may several times re-build same rc- number.

4.2.2. Download and check release build

Download and unzip release archive. It can be found at "Artifacts" tab on build page. Example:

Expand

Code Block
languagebash
themeRDark
linenumberstrue
~/download:[]$ unzip release-2.7.0-rc0.zip


4.2.3. Write down build number (Teamcity identification of builds, usually starts from # symbol). This number will be re-used in future steps.4.2.4.

Do some checks related to release (full list of check to be done can be found in section 5.1):

  • Validate version of Ignite, RC number, and packages versions (from 'packages' folder) are correct.

...

  • Unpack build provided with RC: svn/vote/apache-ignite-

...

  • {$version}-bin.zip . Run Ignite node from resulting apache-ignite-

...

  • {$version}-bin/bin folder.
  • Validate node starts, correct version, and copyright messages produced.

4.2.3.

...

Verify files changes using TeamCity

There is TC task for generating report containing difference comparing current release with previous.

https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency


You should run it and do sanity check for a changed files.

To start the build you need to specify current (staging) version and released version of Apache Ignite. See "Artifacts" tab to get task results. Example:

Expand

Image Added


For 2.7 release "apache-ignite-hadoop" removed and some new dependencies introduced for a benchmarks.

Image Added

4.2.3. Run automated release check step on TC

Run '[3] Apache Ignite Release Vote | Check RC' https://ci.ignite.apache.org/buildConfiguration/ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum


This step will validate hashes, Javadoc, build from sources, licenses. So it it required to run it to simplify/skip some local checks from section 5.1.


Expand

Image Added


4.3. Sign and deploy RC using vote preparation scripts

Run vote scripts to prepare RC before voting. You may skip steps 4.3.1 & step 4.3.2 in case you want to run some testing of release. In case release build was made for testing-only purposes, you can go to step 4.3.3 in this section.

4.3.1. Run script to

Run vote scripts to prepare RC before voting. You may skip steps 4.3.1 & step 4.3.2 in case you want to run some testing of release. In case release build was made for testing-only purposes, you can go to step 4.3.3 in this section.

4.3.1. Run script to create VCS tag in git 

Run script vote_1[git]create_rc_tag.sh  Example of script output:

...

Expand


Code Block
languagebash
themeRDark
$ ./vote_3_step_3\[svn\]deploy_artifacts.sh 
RC 2.7.0-rc0
Adding (binary)  svn/vote/apache-ignite-2.7.0-src.zip
Adding           svn/vote/apache-ignite-2.7.0-src.zip.asc
Adding           svn/vote/apache-ignite-2.7.0-src.zip.sha512
Adding (binary)   svn/vote/apache-ignite-fabric-2.7.0-bin.zip
Adding           svn/vote/apache-ignite-fabric-2.7.0-bin.zip.asc
Adding           svn/vote/apache-ignite-fabric-2.7.0-bin.zip.sha512
Adding (binary)   svn/vote/apache-ignite-hadoopfabric-2.7.0-bin.zip
Adding           svn/vote/apache-ignite-hadoopfabric-2.7.0-bin.zip.asc
Adding           svn/vote/apache-ignite-hadoopfabric-2.7.0-bin.zip.sha512
Committing transaction...
Committed revision 29664.
Adding (binary)   packagingsvn/pkgvote/apache-ignite-hadoop-2.7.0-1bin.noarch.rpm
...

Check binaries and sources are available in the SVN: https://dist.apache.org/repos/dist/dev/ignite/ 

4.4. Verify Release changes using TeamCity

Compare with previous release.

...

To start the build you need to specify current (staging) version and released version of Apache Ignite. See "Artifacts" tab to get task results. Example:

...

Image Removed

For 2.7 release "apache-ignite-hadoop" removed and some new dependencies introduced for a benchmarks.

Image Removed

zip
Adding           svn/vote/apache-ignite-hadoop-2.7.0-bin.zip.asc
Adding           svn/vote/apache-ignite-hadoop-2.7.0-bin.zip.sha512
Committing transaction...
Committed revision 29664.
Adding (binary)  packaging/pkg/apache-ignite-2.7.0-1.noarch.rpm
...




Check binaries and sources are available in the SVN: https://dist.apache.org/repos/dist/dev/ignite/ 

4.4

...

Prepare NuGet staging

Using Teamcity build number from step 4.2.1, run https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages

...

Check results at myget UI, https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite

4.

...

Sending Release For Vote

After the community agrees that the codebase is ready for a release, release manager should send the release for a vote.

...

Warning


6. Unclear how to prepare/update 6.3.11.GCE&AWSvirtualmachines

7. Steps to be done for upload RPM/DEB packages 8. Improve process by fixing and describing TC step with a number of automatic validations https://ci.ignite.apache.org/buildConfiguration/ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum?