gitlab-qa 3.2.1 → 3.2.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/docs/how_it_works.md +1 -1
- data/docs/run_qa_against_gdk.md +6 -6
- data/docs/what_tests_can_be_run.md +2 -2
- data/lib/gitlab/qa/scenario/test/integration/geo.rb +8 -6
- data/lib/gitlab/qa/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: bb67489afb90f2129504bff8b502b95d8cc448ee559e635a5cbf28c0a1ad36b3
|
4
|
+
data.tar.gz: 9629fd028004d72bc0a8d49dd134bd106a0202d08d1995e5abc35cca007c73a2
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 645d08b2fec56595b73cc2ab13c601e20a753c25c7787679a6b17d7968d3082045dd22cb60a1b7139d8056a87861a9e06a4fd7bfac2ded9e8fbab58cb6000908
|
7
|
+
data.tar.gz: e81513069116b704fe1e4bb9ea2a041b07e2733cc487b2c074d21e03d767dfcdd4c66ddb1e791f605a046f255c0df8acf284176693d34578e26ef46ce32fb661
|
data/docs/how_it_works.md
CHANGED
@@ -7,7 +7,7 @@ For a visual architecture explanation, please read the
|
|
7
7
|
|
8
8
|
## What happens when you run `gitlab-qa Test::Instance::Image CE`
|
9
9
|
|
10
|
-
1. `
|
10
|
+
1. `exe/gitlab-qa` calls [`.perform`][instance-image] on the fully qualified constant
|
11
11
|
`Gitlab::QA::Scenario::` + the scenario name, e.g. `QA::Scenario::Test::Instance::Image`
|
12
12
|
1. A new `gitlab-ce` container is started with `Component::Gitlab.perform`
|
13
13
|
1. Then `Component::Specs.perform` is called, which starts a `gitlab/gitlab-qa`
|
data/docs/run_qa_against_gdk.md
CHANGED
@@ -19,10 +19,10 @@ make a few changes to your `gdk/gitlab/config/gitlab.yml` file.
|
|
19
19
|
1. Run the QA scenario as follows:
|
20
20
|
|
21
21
|
```
|
22
|
-
$ gitlab-qa Test::Instance::Any CE http://192.168.0.12:3000 -- qa/specs/features/
|
22
|
+
$ gitlab-qa Test::Instance::Any CE http://192.168.0.12:3000 -- qa/specs/features/browser_ui/1_manage/login/log_in_spec.rb
|
23
23
|
|
24
|
-
# Or if you want to run your local `gitlab-qa/
|
25
|
-
$
|
24
|
+
# Or if you want to run your local `gitlab-qa/exe/gitlab-qa`:
|
25
|
+
$ exe/gitlab-qa Test::Instance::Any CE http://192.168.0.12:3000 -- qa/specs/features/browser_ui/1_manage/login/log_in_spec.rb
|
26
26
|
|
27
27
|
# And if you want to test your local `gdk/gitlab/qa` changes, you'll need to
|
28
28
|
# build the QA image first
|
@@ -30,7 +30,7 @@ make a few changes to your `gdk/gitlab/config/gitlab.yml` file.
|
|
30
30
|
$ docker build -t gitlab/gitlab-ce-qa:your-custom-tag .
|
31
31
|
|
32
32
|
# Then in gitlab-qa:
|
33
|
-
$
|
33
|
+
$ exe/gitlab-qa Test::Instance::Any gitlab/gitlab-ce:your-custom-tag http://192.168.0.12:3000 -- qa/specs/features/browser_ui/1_manage/login/log_in_spec.rb
|
34
34
|
```
|
35
35
|
|
36
36
|
## Run Geo QA tests against your Geo GDK setup
|
@@ -39,10 +39,10 @@ Run from the `gdk-ee/gitlab/qa` directory with GDK primary and secondary running
|
|
39
39
|
|
40
40
|
```
|
41
41
|
# Run in the background
|
42
|
-
bin/qa QA::EE::Scenario::Test::Geo --primary-address http://localhost:3001 --secondary-address http://localhost:3002 --primary-name primary --secondary-name secondary --without-setup
|
42
|
+
$ bundle exec bin/qa QA::EE::Scenario::Test::Geo --primary-address http://localhost:3001 --secondary-address http://localhost:3002 --primary-name primary --secondary-name secondary --without-setup
|
43
43
|
|
44
44
|
# Run in visible Chrome browser
|
45
|
-
CHROME_HEADLESS=
|
45
|
+
$ CHROME_HEADLESS=0 bundle exec bin/qa QA::EE::Scenario::Test::Geo --primary-address http://localhost:3001 --secondary-address http://localhost:3002 --primary-name primary --secondary-name secondary --without-setup
|
46
46
|
```
|
47
47
|
|
48
48
|
### QA Tool support on macOS
|
@@ -14,7 +14,7 @@ host machine.
|
|
14
14
|
## Orchestrated tests
|
15
15
|
|
16
16
|
Orchestrated tests are run with the `gitlab-qa` binary (from the
|
17
|
-
`gitlab-qa` gem), or in the `gitlab-qa` project, with the `
|
17
|
+
`gitlab-qa` gem), or in the `gitlab-qa` project, with the `exe/gitlab-qa` binary
|
18
18
|
(useful if you're working on the `gitlab-qa` project itself and want to test
|
19
19
|
your changes).
|
20
20
|
|
@@ -446,7 +446,7 @@ This scenario functions the same as `Test::Instance::Staging`
|
|
446
446
|
but will run tests against [`pre.gitlab.com`](https://pre.gitlab.com).
|
447
447
|
|
448
448
|
Note that [`pre.gitlab.com`](https://pre.gitlab.com) is used as an Interim
|
449
|
-
Performance Testbed and [will be replaced with the actual testbed in the future](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/60).
|
449
|
+
Performance Testbed and [will be replaced with the actual testbed in the future](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/60).
|
450
450
|
|
451
451
|
### `Test::Instance::Smoke`
|
452
452
|
|
@@ -4,7 +4,7 @@ module Gitlab
|
|
4
4
|
module Test
|
5
5
|
module Integration
|
6
6
|
class Geo < Scenario::Template
|
7
|
-
GIT_LFS_VERSION = '2.
|
7
|
+
GIT_LFS_VERSION = '2.7.2'.freeze
|
8
8
|
|
9
9
|
##
|
10
10
|
# rubocop:disable Lint/MissingCopEnableDirective
|
@@ -24,12 +24,13 @@ module Gitlab
|
|
24
24
|
primary.network = 'geo'
|
25
25
|
primary.omnibus_config = <<~OMNIBUS
|
26
26
|
geo_primary_role['enable'] = true;
|
27
|
-
postgresql['listen_address'] = '0.0.0.0';
|
28
|
-
postgresql['trust_auth_cidr_addresses'] = ['0.0.0.0/0','0.0.0.0/0'];
|
29
|
-
postgresql['md5_auth_cidr_addresses'] = ['0.0.0.0/0'];
|
30
|
-
postgresql['max_replication_slots'] = 1;
|
31
27
|
gitlab_rails['db_key_base'] = '4dd58204865eb41bca93bd38131d51cc';
|
28
|
+
gitlab_rails['geo_node_name'] = '#{primary.name}';
|
32
29
|
gitlab_rails['monitoring_whitelist'] = ['0.0.0.0/0'];
|
30
|
+
postgresql['listen_address'] = '0.0.0.0';
|
31
|
+
postgresql['max_replication_slots'] = 1;
|
32
|
+
postgresql['md5_auth_cidr_addresses'] = ['0.0.0.0/0'];
|
33
|
+
postgresql['trust_auth_cidr_addresses'] = ['0.0.0.0/0','0.0.0.0/0'];
|
33
34
|
sidekiq['concurrency'] = 2;
|
34
35
|
unicorn['worker_processes'] = 2;
|
35
36
|
OMNIBUS
|
@@ -43,9 +44,10 @@ module Gitlab
|
|
43
44
|
secondary.omnibus_config = <<~OMNIBUS
|
44
45
|
geo_secondary_role['enable'] = true;
|
45
46
|
gitlab_rails['db_key_base'] = '4dd58204865eb41bca93bd38131d51cc';
|
47
|
+
gitlab_rails['geo_node_name'] = '#{secondary.name}';
|
48
|
+
gitlab_rails['monitoring_whitelist'] = ['0.0.0.0/0'];
|
46
49
|
sidekiq['concurrency'] = 2;
|
47
50
|
unicorn['worker_processes'] = 2;
|
48
|
-
gitlab_rails['monitoring_whitelist'] = ['0.0.0.0/0'];
|
49
51
|
OMNIBUS
|
50
52
|
secondary.exec_commands = fast_ssh_key_lookup_commands + git_lfs_install_commands
|
51
53
|
|
data/lib/gitlab/qa/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: gitlab-qa
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 3.2.
|
4
|
+
version: 3.2.2
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Grzegorz Bizon
|
8
8
|
autorequire:
|
9
9
|
bindir: exe
|
10
10
|
cert_chain: []
|
11
|
-
date: 2019-05-
|
11
|
+
date: 2019-05-23 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: climate_control
|