How to do a release:
- Figure out what has changed since last release - go to TIS-DEVOPS/ansible/vars/stage/platform.yml and compare the versions with the latest versions in all repos (fastest way is to use GitHub)
For TIS-PROFILE, TIS-TCS e.t.c (i.e. repos that have services within them, the pom version required for release is the one in the service folder.
For TIS-ADMINS-UI, there is no pom file but a package.json. Get the version number from it.
- Finalise the artefacts you want to deploy using jenkins
Navigate to https://build.tis.nhs.uk/jenkins
For all repos that have changed, build and include 'Final Tag'
- Create the release documentation like below → Jira query to add tasks: status = Done AND status changed to Done after 2016-12-07 before now() and fixVersion is EMPTY and project="TIS Development"
Click on Search >> Search all issues >> Enter Query OR Search >> View all issues >> Advanced >> Enter Query
- Create release main.yml inside TIS-DEVOPS → TIS-DEVOPS/ansible/releases/TIS-XX/main.yml → push → make sure https://build.tis.nhs.uk/jenkins/job/devops/ has run
- Release to stage → https://build.tis.nhs.uk/jenkins/job/release-stage-pipeline/
- Ask everyone to check their stuff in stage
- Modify and push TIS-DEVOPS/ansible/vars/prod/platform.yml
- Release to prod → https://build.tis.nhs.uk/jenkins/job/release-prod-pipeline/
- Write up a TIS Notification (you will need the TIS Admin role on prod to create a notification)
- Notify the slack channel
Release Documentation
- In Jira, go to the Releases Page and add a new release name with start date and description.
- Move any issues that have been resolved, or that are planned to be resolved, to this release. The easiest way to do this is to filter down to the results you want and bulk edit them to change the 'Fix Version/s' field to match the release name. Try this filter - Done in current sprint, no fixversion
- Create a new page using the JIRA Report Blueprint by clicking the white elipsis in the page header. Go to "New release" and fill out the details for this release. The JIRA report on that page defaults to beta-002 so that needs to change.
Add the link to Slack's #general channel and mention @channel so all users are notified, e.g.
@channel new release https://hee-tis.atlassian.net/wiki/display/TISDEV/beta-001
Previous Releases
Add Comment