Testing the E2E blog creation for a security release
Overview
This issue is a placeholder for when we test generating the blog post with the new tooling for the next scheduled security release.
Tasks
✅
Part 1: Blog post generation -
Modify a local branch so all notifications are sent to the release-tools-test channel and so no one is assigned to the blog post. -
Create a pipeline using the new branch and setting the ENV variable SECURITY_RELEASE_PIPELINE: release_preparation
. -
Run the security_release:release_preparation:start
job -
Check that the jobs were successful -
Verify the blog post was created on the security repository -
Ping AppSec RMs to take a look at this draft and note any problems -
Close the MR
✅
Part 2: Blog post publishing -
Create an MR on https://gitlab.com/gitlab-org/security/www-gitlab-com that makes a negligible change to the handbook. -
Add the patch release post
label to this MR and make sure there are no other MRs open on that repository with that label. -
Modify a local branch so all notifications are sent to the release-tools-test channel. -
Create a pipeline using the new branch and setting the ENV variable SECURITY_RELEASE_PIPELINE: publish
. -
Run the security_release:publish:start
job -
Check that the jobs were successful -
Verify the test MR was opened on the canonical repo and automatically merged -
Verify the test MR on the security repo was closed
Followup MRs
Followup tasks
-
Re-test Part 2 after the followup MR has been implemented
Edited by Steve Abrams