gitlab-qa 5.4.1 → 5.4.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 79e9a356e7020a43aa03d5fd3a0dc75f4c90438c69cc2eaf9a8c2d0f8a034ffc
-  data.tar.gz: e1694bf700beabf8a30884b353eada1b16a3165af554db070c7dd3ea3df81210
+  metadata.gz: 6ce58eec53ccc54effca3fc1b94070e6ec6f930c13e11aef8dafb600c59feb59
+  data.tar.gz: 97437cf5d0bed65931c57af0dc459d6097f37f3787ba8498f9784d4c45158d2a
 SHA512:
-  metadata.gz: ae9b5c865beacbba24603a23166d9923afc94612c4177ee3cba34a5d5b0048adb8960c802d3f3e054eb10319295e2afc5fca098ad0d63654c58bf6cdffb8df65
-  data.tar.gz: d047164c69791b0a22e39860baaa69beee74535c64c34c95db672866e76d4616a085890c719a83213546fc12a6a0761732584e0175775a2f43ce1b44071e899d
+  metadata.gz: 5ecabb59dd4285a6a0923a680390e6ba7f87eeb85b58827279ebb06870ea32695218ded6a8b78bdaec1d6c4a522d5ed60d888859b6c0dd45c56aa9611a782350
+  data.tar.gz: 46970e6a919d479d104dc664f249b7aa03543e4e95499e7e7912381e02cb383085ea837b61b1e3dfb74eeb6cf50c12ee9ee46e4a5b25a7e4448427fe1bd02622

data/README.md

@@ -12,10 +12,10 @@
   GitLab QA framework and Capybara to setup and perform individual end-to-end
   tests against a live GitLab instance.
   Located at [`gitlab-org/gitlab-ce@qa/qa/specs/features/`][instance-level-scenarios].
-- **GitLab QA orchestrator** (this project): An orchestration tool that enables 
+- **GitLab QA orchestrator** (this project): An orchestration tool that enables
   running various QA test suites in a simple manner.
 - **GitLab QA orchestrated scenarios**: Scenarios where containers are started,
-  configured, and execute instance-level scenarios against a running GitLab 
+  configured, and execute instance-level scenarios against a running GitLab
   instance.
   Located at [`gitlab-org/gitlab-qa@lib/gitlab/qa/scenario/test/`][orchestrated-scenarios].
 
@@ -39,7 +39,7 @@ merge request, even before merging code into the `master` branch.
 ### We can run tests against any instance of GitLab
 
 GitLab QA is a click-driven, black-box testing tool. We also use it to run
-tests against the staging environment, and we strive to make it useful for our 
+tests against the staging environment, and we strive to make it useful for our
 users as well.
 
 ### GitLab QA tests running in the CI/CD environment
@@ -60,8 +60,8 @@ To make it easier to reproduce test failures locally we have published the
 `gitlab-qa` gem [on rubygems.org](https://rubygems.org/gems/gitlab-qa) and we
 are using exactly the same approach to run tests in the CI/CD environment.
 
-It means that using the `gitlab-qa` CLI tool, which orchestrates the test 
-environment and runs the GitLab QA test suite, is a reproducible way of running 
+It means that using the `gitlab-qa` CLI tool, which orchestrates the test
+environment and runs the GitLab QA test suite, is a reproducible way of running
 tests locally and in the CI/CD environment.
 
 It also means that we cannot have custom code in `.gitlab-ci.yml` to, for
@@ -70,16 +70,16 @@ example, start new containers / services.
 ### Test the installation / deployment process too
 
 We distribute GitLab in a package (like a Debian package or a Docker image) so
-we want to test the installation process to ensure that our package is not 
+we want to test the installation process to ensure that our package is not
 broken.
 
 But we are also working on making GitLab be a cloud native product. This means
-that, for example, using Helm becomes yet another installation / deployment 
+that, for example, using Helm becomes yet another installation / deployment
 process that we want to test with GitLab QA.
 
 Considering our goal of being able to test all changes in merge requests, it is
 especially important to be able to test our Kubernetes deployments, as that is
-essential to scaling our test environments to efficiently handle a large number 
+essential to scaling our test environments to efficiently handle a large number
 of tests.
 
 ## Documentation
@@ -88,14 +88,15 @@ of tests.
 - [How it works](docs/how_it_works.md)
 - [Release process](docs/release_process.md)
 - [Run QA tests against your GDK setup](docs/run_qa_against_gdk.md)
+- [Running specific orchestrated tests](docs/running_specific_orchestrated_tests.md)
 - [Trainings](docs/trainings.md)
 - [Waits](docs/waits.md)
 - [What tests can be run?](docs/what_tests_can_be_run.md)
 
 ## How do we use it
 
-Currently, we execute the test suite against GitLab Docker images created by 
-Omnibus nightly via a pipeline in the [nightly](https://gitlab.com/gitlab-org/quality/nightly) 
+Currently, we execute the test suite against GitLab Docker images created by
+Omnibus nightly via a pipeline in the [nightly](https://gitlab.com/gitlab-org/quality/nightly)
 project.
 
 We also execute the test suite nightly against our [staging environment](https://staging.gitlab.com)
@@ -125,7 +126,7 @@ Note: The GitLab QA tool requires that [Docker](https://docs.docker.com/install/
 Scenarios (test cases) and scripts to run them are located in the
 [CE](https://gitlab.com/gitlab-org/gitlab-ce/tree/master/qa) and
 [EE](https://gitlab.com/gitlab-org/gitlab-ee/tree/master/qa)
-repositories under the `qa/` directory, so please also check the documentation 
+repositories under the `qa/` directory, so please also check the documentation
 there.
 
 ## Contributing

data/docs/running_specific_orchestrated_tests.md

@@ -0,0 +1,11 @@
+# Running specific orchestrated tests
+
+## Maven artifact spec
+
+The [maven repository spec](https://gitlab.com/gitlab-org/gitlab/-/blob/master/qa/qa/specs/features/ee/browser_ui/5_package/maven_repository_spec.rb) creates a Maven artifact and links it to a GitLab project. The artifact is created within a [Maven docker image](https://gitlab.com/gitlab-org/gitlab/-/blob/master/qa/qa/service/docker_run/maven.rb#L8).
+
+Using `gitlab-qa` to run these tests reduces the liklihood of network errors between the maven container and GitLab instance.
+
+To run this with `gitlab-qa` you can use the `Test::Instance::Image` that is needed for your test. For example:
+
+`gitlab-qa Test::Instance::Image registry.gitlab.com/gitlab-org/build/omnibus-gitlab-mirror/gitlab-ee:2cb9a85d2beadd51b926eaddb05005403bee0013 -- --tag orchestrated qa/specs/features/ee/browser_ui/5_package/maven_repository_spec.rb` - runs the test against a specific Omnibus GitLab image that was built through `package-and-qa`.

data/lib/gitlab/qa/report/results_in_issues.rb

@@ -234,7 +234,7 @@ module Gitlab
           # because the other pipelines will be monitored by the author of the MR that triggered them.
           # So we assume that we're reporting a master pipeline if the project name is 'gitlab-qa'.
 
-          Runtime::Env.ci_project_name == 'gitlab-qa' ? 'master' : Runtime::Env.ci_project_name
+          Runtime::Env.ci_project_name.to_s.start_with?('gitlab-qa') ? 'master' : Runtime::Env.ci_project_name
         end
       end
     end

data/lib/gitlab/qa/version.rb

@@ -1,5 +1,5 @@
 module Gitlab
   module QA
-    VERSION = '5.4.1'.freeze
+    VERSION = '5.4.2'.freeze
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: gitlab-qa
 version: !ruby/object:Gem::Version
-  version: 5.4.1
+  version: 5.4.2
 platform: ruby
 authors:
 - Grzegorz Bizon
@@ -225,6 +225,7 @@ files:
 - docs/release_process.md
 - docs/run_qa_against_gdk.md
 - docs/running_against_remote_grid.md
+- docs/running_specific_orchestrated_tests.md
 - docs/trainings.md
 - docs/waits.md
 - docs/what_tests_can_be_run.md