...
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.
Download and unzip release archive. It can be found at "Artifacts" tab on build page. Example:
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
|
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):
...
...
...
...
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 |
---|
For 2.7 release "apache-ignite-hadoop" removed and some new dependencies introduced for a benchmarks. |
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 |
---|
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.
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.
Run script vote_1[git]create_rc_tag.sh Example of script output:
...
Expand | |||||||
---|---|---|---|---|---|---|---|
|
Check binaries and sources are available in the SVN: https://dist.apache.org/repos/dist/dev/ignite/
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:
...
For 2.7 release "apache-ignite-hadoop" removed and some new dependencies introduced for a benchmarks.
|
Check binaries and sources are available in the SVN: https://dist.apache.org/repos/dist/dev/ignite/
...
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
...
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? |