Skip to content

Require upgrade stop at 16.7

Clemens Beck requested to merge 8284-upgrade-stop-16-7 into master

What does this MR do?

Require upgrade stop at 16.7

GitLab 16.7 is a required upgrade stop for 16.8.

See: https://docs.gitlab.com/ee/update/#upgrade-paths

Changelog: changed

Related issues

Closes #8284 (closed)

Test Plan

  1. Install GitLab 16.6.x

  2. Attempt to upgrade to 16.8.x (use the package/image with stubbed version info of https://gitlab.com/gitlab-org/omnibus-gitlab/-/pipelines/1125292634)

    Expectation: Upgrade should be blocked.

  3. Attempt to upgrade to 16.7.x

    Expectation: Upgrade should succeed.

  4. Attempt to upgrade to 16.8.x (use the package/image with stubbed version info of https://gitlab.com/gitlab-org/omnibus-gitlab/-/pipelines/1125292634)

    Expectation: Upgrade should succeed.

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • MR title and description are up to date, accurate, and descriptive.
  • MR targeting the appropriate branch.
  • Latest Merge Result pipeline is green.
  • When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow.

For GitLab team members

If you don't have access to this, the reviewer should trigger these jobs for you during the review process.

  • The manual Trigger:ee-package jobs have a green pipeline running against latest commit.
  • If config/software or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
  • If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline must succeed.
  • If CI configuration is changed, the branch must be pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes.
  • Documentation created/updated.
  • Tests added.
  • Integration tests added to GitLab QA.
  • Equivalent MR/issue for the GitLab Chart opened.
  • Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.
Edited by Clemens Beck

Merge request reports