...
Scheduled Releases
A release will typically be produced once all the tickets in the associated sprint are complete.
However, it is likely that Fran Benoy-Deeney about any releases to be made.
Builds from the Bamboo process are available here:
\\rr-bamboo.northbristol.local\<Product>\<Branch Label>\<ISODate.BambooBuildNumber>
When the code is ready to be released,
...
will want the changeover to happen on a particular day to minimise disruption to staff, particularly if some are mid-way through processing files.
To let Fran know what will be in the build go to the Sprint and each of the "Done" tickets. Any which have resulted in a change to the program (so not "don't fix" or "can't reproduce") and make sure that the "Fix Version" is set to this release.
Make a release page by copying one such as https://confluence.renalregistry.nhs.uk/display/RR/1.1.11 and modifying the Jira component to return tickets from the new version. Blank the release date.
The steps are -
1) Create a Pull Request for the branch for each of the components in BitBucket and merge it into Master. Do not tick the option to delete the branch.
| Note |
|---|
TODO: rr_git should have a command to do this. |
2) Checkout Master into a new directory with
| Code Block |
|---|
rr_git.py --destination C:/MyWork/UKRR/Master |
| Warning |
|---|
Despite not supplying branch_label this seems to clone the sub-packages using the branch ID from the requirements.txt files. Make sure to checkout master in each directory before doing the next actions. It also seems not to work if the output directory already exists. In this situation a "pull" is also required. |
(Amend path as required)
4) Remove references to the branch from the requirements.txt in the repos under the master folder. Push afterwards.
Note that this requires
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
3) Tag the branch with -
| Code Block |
|---|
rr_git.py --action tag --tag-label vY.Y.Y --destination C:/MyWork/UKRR/Master |
Y.Y.Y here should be the version being released.
| Note |
|---|
Git, or at least the version of Git on my PC breaks if a tag and branch exist with the same names. This is why I have the tag labels prefixed with a 'v'. |
5) A new build should have been made under
| Code Block |
|---|
\\rr-bamboo\Registry_Test_Utils\PRODUCT |
| Info |
|---|
This should be identical to the build that is under \\rr-bamboo\Registry_Utils\PRODUCT\BRANCH . I have suggested using the Master build as a check the merge has completed correctly but there may be arguments for the reverse. |
6) Copy the build to R:\registry_utils\<Product>\<Branch>
...
7) Modify R:\registry_utils\
...
PRODUCT\run.bat
...
to change which folder the executable is found in.
8) Update the Release page with the date that it was released.
9) Set the Jira version to Released.
Go to the "Renal Registry" project page and click the Settings ("Cog") button in the lower left hand corner. You should then see a Versions section and an entry for the version that's just been closed. Edit it to set it released and add the release date.
