Skip to content

Drop tracking issue mention from critical security template

What does this MR do and why?

  • Critical security releases don't require tracking issues. This commit removes the tracking issue mention from the security template
  • Adds quotes to the ChatOps message posted in the logs when the notify_release_complete job fails. This facilitates release managers to just copy and paste it.

Examples

Regular security release

Click to expand

Security patch release: 16.3.5, 16.2.8, 16.1.6

2023-09-18 15:17:55.496038 D [dry-run] ReleaseTools::GitlabClient -- [HTTParty] [2023-09-18 15:17:55 -0600] 200 "GET https://gitlab.com/api/v4/projects/gitlab-org%2Fgitlab/issues" -

First steps

  • Set the Due date on this issue with the planned Security publish date
  • Start the security_release_prepare:start job in the security release pipeline: foo
    • Ensure the security_release:prepare stage completes before continuing to the next section.
  • Check if the security release tracking issue contains any linked issues for projects under GitLab managed versioning (cng-ee, gitaly, gitlab-pages, omnibus-gitlab-ee).
  • Modify the dates below to accurately reflect the plan of action.

Critical security release

Click to expand

First steps

  • Set the Due date on this issue with the planned Security publish date

  • Start the security_release_prepare:start job in the security release pipeline: foo

    • Ensure the security_release:prepare stage completes before continuing to the next section.
  • Check if the security fix is associated with any of the projects under GitLab managed versioning (cng-ee, gitaly, gitlab-pages, omnibus-gitlab-ee).

  • Post a message to #g_dedicated-team channel in Slack to inform about this critical security release. Dedicated will need to make a plan to patch their installations.

Author Check-list

  • Has documentation been updated?

Merge request reports