diff options
author | Amine <amine@mouafik.fr> | 2020-05-13 04:33:34 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-05-13 04:33:34 +0000 |
commit | 6c4b2cbde95d0280c8d2fce9e64397523146f245 (patch) | |
tree | 6ec0e6c4b81bb06af6edf41cfdff4aee1e8a067f /README.md | |
parent | Use Tray popUpContextMenu on macOS/Windows only (#741) (diff) | |
download | ferdium-app-6c4b2cbde95d0280c8d2fce9e64397523146f245.tar.gz ferdium-app-6c4b2cbde95d0280c8d2fce9e64397523146f245.tar.zst ferdium-app-6c4b2cbde95d0280c8d2fce9e64397523146f245.zip |
Setup nightly releases deployment pipeline (#730)
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 23 |
1 files changed, 19 insertions, 4 deletions
@@ -282,18 +282,33 @@ Deliverables will be available in the `out` folder. | |||
282 | 282 | ||
283 | ### Release | 283 | ### Release |
284 | 284 | ||
285 | Create a new [draft release](https://github.com/getferdi/ferdi/releases/new) that targets the `release` branch, then: | ||
286 | |||
287 | ```bash | ||
288 | $ git checkout develop && git pull | ||
289 | $ git checkout release | ||
290 | $ git submodule update --remote --force | ||
291 | $ git add . | ||
292 | $ git commit -m "Update submodules" | ||
293 | $ git merge --no-ff develop | ||
294 | $ git push | ||
295 | ``` | ||
296 | |||
297 | Once the draft release assets are uploaded (13 assets), publish the release. The last commit of the `release` branch will be tagged. You can then merge `release` into `master` and back into `develop` if needed. | ||
298 | |||
299 | #### Nightly | ||
300 | |||
285 | ```bash | 301 | ```bash |
286 | $ git checkout develop && git pull | 302 | $ git checkout develop && git pull |
303 | $ git checkout nightly | ||
287 | $ git submodule update --remote --force | 304 | $ git submodule update --remote --force |
288 | $ git add . | 305 | $ git add . |
289 | $ git commit -m "Update submodules" | 306 | $ git commit -m "Update submodules" |
290 | $ git checkout master | ||
291 | $ git merge --no-ff develop | 307 | $ git merge --no-ff develop |
292 | $ git tag v5.3.4-beta.4 | 308 | $ git push |
293 | $ git push --tags | ||
294 | ``` | 309 | ``` |
295 | 310 | ||
296 | When pushing a new tag, the CI builds will create a draft GitHub release and upload the deliverables in the draft release assets. Wait for all the assets to be uploaded before publishing the draft release. | 311 | The draft release and assets will be available in [getferdi/nightlies releases](https://github.com/getferdi/nightlies/releases). You need to manually publish the draft release as a pre-release for now. |
297 | 312 | ||
298 | ## Contributors ✨ | 313 | ## Contributors ✨ |
299 | 314 | ||