Fix buginess when blog post is moved from security to canonical
Overview
When we used the MoveBlogPost
tooling for the first time during the last security release, it failed to properly move the blog post to canonical. It created an empty MR. A few problems were seen:
- The MoveBlogPost service failed to push the branch to canonical, but the job still succeeded and an empty merge request was opened.
- Something else happened where we finally saw the changes show up, but it said the branch did not exist, yet the commits did (very confusing):
Some of this may have been due to the branch having been created and used multiple times in the previous week while the new tooling was being tested, but we need to investigate and make sure we have these problems fixed before the next release.
Implementation steps
-
Update the publish services to use API rather than Git operations gitlab-org/release-tools!2757 (merged) -
Close and delete branch from the security repo https://gitlab.com/gitlab-org/security/www-gitlab-com/-/merge_requests/169 -
Close the merge request and delete branches from the canonical repo -
Update with the findings #19742
Edited by Mayra Cabrera