Add slack notifications when security blog post is generated
Overview
In #19705 (closed) and gitlab-org/release-tools!2695 (merged) we added a new stage and job to the security release pipeline for generating the blog post. The job currently runs the release:patch_blog_post
rake task.
Jobs in the security release pipeline should notify release managers if they have succeeded or failed in #f_upcoming_release
.
Proposal
Update the release:patch_blog_post
task so if it is triggered by the security release pipeline (env[SECURITY_RELEASE_PIPELINE] = true
) then it should include slack notifications using ReleaseTools::Slack::ReleaseJobEndNotifier
. If the job fails, the job output should include instructions of how to manually trigger the blog post creation (which might just be manually triggering the same rake task). See other pipeline tasks for how this normally is formatted. It will likely require creating a new class like ReleaseTools::Security::ReleasePreparation::GenerateBlogPost
to manage all of the logic that currently exists in the rake task along with these slack notifications.
A bonus would be to include a link to the created blog post MR in a slack notification. This is not essential, however since release managers will automatically be assigned to the MR.