This page lists a number of tips and tricks we have found useful in day to day Quality Engineering related tasks.
While working on the GitLab-QA codebase, it is sometimes helpful to run the GitLab-QA pipeline
against a specific release of the GitLab project. This could be
due reasons such as that particular GitLab release containing specific code needed for validating the changes made
in Gitlab-QA. To run a GitLab-QA pipeline against
a specific GitLab release, we need to know the GitLab release version created and tagged by the omnibus pipeline.
This can be found by either observing the
RELEASE variable in any of the
package-and-qa test jobs or
in the last output line of the
Trigger:gitlab-docker job triggered by the
package-and-qa job. Here is an example of what the
Copy this string and create a new GitLab-QA pipeline
RELEASE variable and use the copied string as its value. Run the pipeline against the branch that
has your changes.
To find out the version, revision, branch and package deployed in gitlab.com, staging and canary environments, run this in the #chat-ops-test Slack channel:
/chatops run auto_deploy status
You will need access to the https://ops.gitlab.net/gitlab-com/chatops project to run
Ask to be added to this project in the #development Slack channel.
If you have a revision SHA that is deployed on an environment, you can find out if a change has made it to that environment.
For example, if the revision SHA deployed on an environment is
c46489109e4 and you want to find out if a change in
restrict_by_ip_address_spec.rb has made it there, you can use:
git show c46489109e4:qa/qa/specs/features/ee/browser_ui/1_manage/group/restrict_by_ip_address_spec.rb
You can determine the revision SHA deployed on a GitLab instance by either navigating to www.example.com/help,
by calling the
http://www.example.com/api/v4/version API or by running
/chatops run auto_deploy status in a Slack
channel such as #chat-ops-test.
You can also determine if your commit has been deployed on a GitLab environment using ChatOps.
For example, if your commit ref is
347e530c5b3dec60c0ce2870bc79ca4c8273604d you can run this command in a Slack
channel such as #chat-ops-test:
/chatops run auto_deploy status 347e530c5b3dec60c0ce2870bc79ca4c8273604d
The commit SHA for a nightly pipeline can be determined in the following ways:
Run the nightly docker image
docker run \ --hostname localhost \ --publish 443:443 --publish 80:80 --publish 22:22 \ gitlab/gitlab-ee:nightly
The commit SHA can be determined by visiting the http://localhost/help page after sign-in
or by calling the
/api/v4/version API where it is displayed as a value of the
Nightly images are created by scheduled pipelines here: https://dev.gitlab.org/gitlab/omnibus-gitlab/pipeline_schedules
You can look at the last pipeline by clicking the pipeline number for CE nightly or EE nightly under the "Last pipeline" column.
In the pipeline view click a job under the "Gitlab_com:package" column. The SHAs for GitLab Components
are listed towards the end of the logs. The GitLab commit SHA is displayed as a value of