Skip to content

Add support for OpenSUSE 15.4

Andrew Patterson requested to merge 6876-packages-for-opensuse-15.4 into master

What does this MR do?

Adds support for building OpenSUSE LEAP 15.4 Omnibus packages.

Related issues

Related #6876 (closed)

Test plan

Setup

  1. Install gitlab and set root password.

  2. Edit /etc/ssh/sshd_config:

    #Match User git    # Apply the AuthorizedKeysCommands to the git user only
    #  AuthorizedKeysCommand /opt/gitlab/embedded/service/gitlab-shell/bin/gitlab-shell-authorized-keys-check git %u %k
    #  AuthorizedKeysCommandUser git
    #Match all    # End match, settings apply to all users again
    AcceptEnv GIT_PROTOCOL
  3. Set environment variables

    export GITLAB_VERSION=nightly
    export GITLAB_USERNAME=root
    export GITLAB_PASSWORD="<password>
    export GITLAB_ADMIN_USERNAME=${GITLAB_USERNAME}
    export GITLAB_ADMIN_PASSWORD=${GITLAB_PASSWORD}
    export GITLAB_URL="instance FQDN}
    export EE_LICENSE=$(cat <license file path)
    export GITHUB_ACCESS_TOKEN="<token>" # PAT from 1Passed gitlab-qa+github@gitlab.com.
    export CHROME_DISABLE_DEV_SHM=true
    
  4. Pull docker image

    docker pull gitlab/gitlab-ee-qa:$GITLAB_VERSION
  5. Make sure you are running ruby 2.5 with gitlab-qa gem installed.

  6. Start test

    Run full QA test suite as shown in https://gitlab.com/gitlab-org/charts/gitlab/-/blob/a648ce8ce3e0dc3e8a6729c26aac874b605c3fa9/doc/development/gitlab-qa/index.md

    export QA_OPTIONS="--tag ~skip_live_env --tag ~orchestrated --tag ~requires_praefect --tag ~github --tag ~requires_git_protocol_v2 --tag ~transient"
    gitlab-qa Test::Instance::Any EE:$GITLAB_VERSION $GITLAB_URL -- $QA_OPTIONS

Run tests for the following platforms:

  • Green pipeline including Trigger:ee-package and Trigger:ce-package. Run build-package-on-all-os for both triggers.
  • Run gitlab-qa on OpenSUSE 15.4 x86_64
  • Run gitlab-qa on OpenSUSE 15.4 aarch64

Checklist

See Definition of done.

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

Required

  • Merge Request Title, and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks
  • trigger-package has a green pipeline running against latest commit

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

Closes #6876 (closed)

Edited by Andrew Patterson

Merge request reports