Skip to content

Add deprecation message for openSUSE 15.4

DJ Mountney requested to merge deprecate-opensuse-15-4 into master

What does this MR do?

Add deprecation message for openSUSE 15.4

We will stop building packages for openSUSE 15.4 by GitLab 16.8

Related issues

Part of #8212 (closed)

Test Plan

  1. Setup a OpenSUSE Leap 15.4 instance
    • You can launch one up via the dev-distribution group in AWS if you are a distribution team member
  2. Download and Install the openSUSE 15.4 package
    • sudo zypper install ./gitlab-*.rpm
  3. Run reconfigure and see the deprecation message at the end of the output
    • sudo gitlab-ctl reconfigure
  4. See deprecation message
Deprecations:
Your OS, opensuseleap-15.4, will be deprecated soon.
Starting with GitLab 16.8, packages will not be built for it.
Switch or upgrade to a supported OS, see https://docs.gitlab.com/ee/administration/package_information/supported_os.html for more information.

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 Robert Marshall

Merge request reports