Skip to content

Commit b64635d

Browse files
committed
document updates
1 parent aaf8f05 commit b64635d

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

docs/new-release-procedure.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -14,21 +14,23 @@
1414
### Ensure release passes Test
1515
- `gradle :firefly:test`
1616

17-
### Commit and Tag
17+
### Commit, Tag, push tags
1818
- Commit your changes - _example message:_ "Release 2024.1.0: document updates"
19-
- Tag the `rc-yyyy.m` branch with the release `release-yyyy.m.r`
19+
- Push your changes
20+
- Tagging: `buildScript/next-release-tag.sh`
21+
- `next-releaase-tag.sh` will tag and push
22+
- Tags are make in the form `rc-yyyy.m` branch with the release `release-yyyy.m.r`
2023
- _Example:_
2124
- the second release from branch `rc-2024.1` with the git tagged with `release-2024.1.1`
2225
- `git tag release-2024.1.1`
23-
24-
### Push
25-
- Push to GitHub
26-
- push the rc: _example:_ `git push origin rc-2024.1`
27-
- push the tags: `git push origin --tags`
26+
- the script will also create docker tag for the next step
2827

2928
### Build docker images and deploy it to IRSA Kubernetes
3029
- Best to use Jenkins: https://irsajenkins.ipac.caltech.edu/job/firefly/build
31-
- Build the docker with the following docker tags: `rc-yyyy.m,yyyy.m,yyyy.m.r,latest` (comma-separated without spaces)
30+
- Build the docker images with Jenkins
31+
- _Important_ -`buildscript/next-releaase-tag.sh` should produce the docker tags
32+
- just cut and paste them
33+
- it wil prouce the following docker tags: `rc-yyyy.m,yyyy.m,yyyy.m.r,latest` (comma-separated without spaces)
3234
- _example:_ from the example above the release would be built with: `rc-2024.3`, `2024.3`,`2024.3.1`, `latest`
3335
- `BUILD_ENV`: Select 'ops'
3436
- `ACTION`: Select 'both'

0 commit comments

Comments
 (0)