You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/releasing-workflow-instructions.md
+3-7Lines changed: 3 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,8 +18,6 @@ with:
18
18
- BUILD_TIME is the build time
19
19
- GIT_SHA is the git SHA corresponding to the code used for building
20
20
21
-
see [docs/img/git-release-workflow.svg](docs/img/git-release-workflow.svg)
22
-
23
21
### Example
24
22
25
23
The ``webserver`` service in master branch with commit ``752ef...`` will be built by ``github`` actions CI on ``2020/08/31`` at ``12:36`` and therefore the image is named as:
@@ -43,8 +41,6 @@ with:
43
41
- BUILD_TIME is the build time
44
42
- GIT_SHA is the git SHA corresponding to the code used for building
45
43
46
-
see [docs/img/git-release-workflow.svg](docs/img/git-release-workflow.svg)
47
-
48
44
### Staging example
49
45
50
46
Just before the review of the ``DAJIA`` sprint we release a staging version ``v1.0.0``, the commit ``752ef...`` from above is tagged as stage and the ``github`` actions CI on ``2020/09/01`` at ``17:30``.
@@ -88,8 +84,6 @@ with:
88
84
- BUILD_TIME is the build time
89
85
- GIT_SHA is the git SHA corresponding to the code used for building
90
86
91
-
see [docs/img/git-release-workflow.svg](docs/img/git-release-workflow.svg)
92
-
93
87
### Release example
94
88
95
89
The team decides to release to production the lastest staging version of ``DAJIA`` sprint. Next release version, following semantic versioning and previous releases, is `v5.6.0`. The images will be retaged by github actions CI as:
@@ -122,7 +116,7 @@ Once ready, the release-hotfix process starts by leveraging Github release mecha
122
116
123
117
Each docker build marked as released are tagged as described in the Release process.
124
118
125
-
see [docs/img/git-hotfix-workflow.svg](docs/img/git-hotfix-workflow.svg)
119
+
see 
126
120
127
121
### Hotfix example
128
122
@@ -146,3 +140,5 @@ A bug was found in version 1.2.0 of the simcore stack. The team decides to fix i
146
140
2. Adjust the list of changes if needed
147
141
3. Press the **Publish release** button
148
142
4. The CI will be automatically triggered and will deploy the staging release
143
+
144
+
see 
0 commit comments