Move deployment tracking out of the deployer and in the release tools
In https://ops.gitlab.net/gitlab-com/gl-infra/deploy-tooling/merge_requests/212 we change the deployment tracking to better track deployments of tag releases and such. Soon we also need to change this to properly track security releases, as these merge requests will reside in a different project.
Now that the code is getting complex enough I think it is time to move all this into the release tools project. The deployer then just triggers a CI pipeline with the right variables. This allows us to reuse everything the release tools project has to offer, and keeps the deployment tooling code simple.
TODO
-
Port tracking of deployments using the API to Release Tools: gitlab-org/release-tools!809 (merged) -
Port creating of workflow comments gitlab-org/release-tools!816 (merged) -
Generate QA issues from Release Tools using the API data: gitlab-org/release-tools!834 (merged) -
Remove tracking of deployments using the API from the deploy-tooling project: https://ops.gitlab.net/gitlab-com/gl-infra/deploy-tooling/merge_requests/232/ -
Remove QA issue code from the deploy-tooling project, and replace with a simple script that schedules a Release Tools pipeline to generate the QA issue: https://ops.gitlab.net/gitlab-com/gl-infra/deploy-tooling/merge_requests/232/ -
Update the deployer to use Release Tools for tracking of deployments -
#673 (closed)
Edited by Yorick Peterse