Add move_blog_post job to security release pipeline
Overview
We need a dedicated stage (security_release_publish
) for the steps run on the release day. This issue should focus on adding the following jobs:
-
security_release_publish:start
job as well to manually start the stage similar to what we have for the prepare and finalize stages. -
security_release_publish:move_blog_post
- This job should call the service created on #19706 (closed)
#19708 (closed) will separately add a job for merging and deploying the blog post.
Update the security_patch.md.erb
template, removing
**Consider communicating with the AppSec counterpart before publishing to sync on the time of releasing the blog post. Emails to the security mailing list are normally handled as a follow up task and should not delay release tasks**
...
- [ ] Notify AppSec counterparts they can submit the blog post to `https://gitlab.com/gitlab-com/www-gitlab-com/
...
from the ## Release
section and adding:
- [ ] Verify with AppSec release managers if the blog post is ready to be published
- [ ] Start the `security_release_publish:start` stage of the security release pipeline: <%= security_pipeline.web_url %>
The rake task called by this job needs to call a new class that will post slack notifications to f_upcoming_releases
to notify if the job was successful or not. It should use the CopyMergeRequestToCanonical
class to copy the MR to canonical.
Edited by Steve Abrams