Timeline for How to handle large deployments using tools like gitlab and docker
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 2, 2018 at 15:24 | history | edited | simbo1905 | CC BY-SA 4.0 |
deleted 2 characters in body
|
| Nov 30, 2018 at 18:49 | comment | added | simbo1905 | @azeko to your specific question if you run a docker build due to a git release event you can parse the git tag out of the release event payload, git checkout that version of the code, build it, push it to the docker repo, then tag it in the docker repo with the same tag. with OKD builds that OCD manages its done slightly differently to work around that OKDs s2i buids don't make it easy to just do a docker tag at the end. | |
| Nov 30, 2018 at 18:40 | comment | added | simbo1905 | @azeko a release event in git fires a release git webhook that triggers a build that makes an image that is given the same tag in the docker registry. then to release that version of the code you tag the repo that holds yaml that names all the versions to deploy to the environment. a second release event in git then runs a build that deploys look at the versions named in the yaml and applies that to the environment. various build tools can be configured to automatically build or deploy or both on git tags. | |
| Nov 30, 2018 at 18:09 | comment | added | azeko | How do you pass docker tag from build repository to deploy repository without manually adding it | |
| Nov 29, 2018 at 23:13 | history | edited | simbo1905 | CC BY-SA 4.0 |
deleted 65 characters in body
|
| Nov 29, 2018 at 23:08 | history | edited | simbo1905 | CC BY-SA 4.0 |
deleted 65 characters in body
|
| Nov 29, 2018 at 23:01 | history | edited | simbo1905 | CC BY-SA 4.0 |
deleted 65 characters in body
|
| Nov 29, 2018 at 22:46 | history | answered | simbo1905 | CC BY-SA 4.0 |