How to release Trace Matcher » History » Version 2
Sergey Smolov, 05/25/2017 02:36 PM
| 1 | 1 | Sergey Smolov | h1. How to release Trace Matcher |
|---|---|---|---|
| 2 | |||
| 3 | The following algorithm cannot be applied without granting an access to the internal network of the ISP RAS. |
||
| 4 | |||
| 5 | To release the Trace Matcher tool do the following: |
||
| 6 | |||
| 7 | * Prepare ChangeLog file, then commit it. |
||
| 8 | 2 | Sergey Smolov | * Go to the Jenkins GUI, enter the "Trace_Matcher_Release" item and select "Build Now" option. If the building process was successful (see "Console Output" tab for more details), the tool binary distribution should be upload to the local Nexus update server. |
| 9 | 1 | Sergey Smolov | * Close the resolved\verified issues on Redmine, mark them as published at the presented build. |
| 10 | * Create the Git tag manually and push it to the server: |
||
| 11 | <pre> |
||
| 12 | git tag <tag-number> |
||
| 13 | git push origin <tag-number> |
||
| 14 | </pre> |
||
| 15 | * Pack the tagged sources into the *.tar.gz archive: |
||
| 16 | <pre> |
||
| 17 | git archive <tag-number> | gzip > /path/to/the/TAR/archive |
||
| 18 | </pre> |
||
| 19 | * Upload the archive to the "Files" tab of project page. |
||
| 20 | * Publish the releas on a "News" tab of project page. |