stage | group | info | title |
---|---|---|---|
Systems |
Distribution |
To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments |
Upgrading Chef |
Chef is a major part of omnibus-gitlab
, and periodically needs to be updated. Follow these steps
to upgrade to the latest version and verify the functionality.
-
Create a new branch in
omnibus-gitlab
git switch -c upgrade-chef-to-X
-
Update the appropriate software entries in
config/templates/omnibus-gitlab-gems/Gemfile
. -
In the
config/templates/omnibus-gitlab-gems
directory, runbundle update
for the updated gems:bundle update chef ohai
-
Update entries in
Gemfile
to the new version. At a minimum, thechef
andohai
entries will need to be updated. -
Update the bundle
- If this is a major version upgrade
bundle update chef ohai
- If this is a minor version upgrade
bundle update chef ohai --conservative
It may be necessary to chase down errors related to dependencies being upgraded
-
Commit the changes
git add config/templates/omnibus-gitlab-gems/Gemfile{,.lock} git add Gemfile{,.lock} git commit git push
-
Ensure the pipelines pass on GitLab.com
-
Trigger an EE package pipeline to ensure we get a
gitlab-qa
run -
When available, trigger an HA validation job
-
Check QA jobs for the package pipeline, and the HA validation job, ensure pipelines are green, or any failures are unrelated.
-
Push to
omnibus-gitlab
ondev.gitlab.org
and ensure the package builds on all platforms -
Download a package to a dev environment, and verify you can upgrade from an older version of
omnibus-gitlab
, to the newer package -
Verify a Geo installation is successful using the newer package
- Read through the Changelog and Release notes, identify any improvements, new features, or bug fixes which may apply to omnibus and open follow up issues