Project

General

Profile

Gitlab Need To Know » History » Version 1

rainerkoenig, 2021-09-10 15:45

1 1 rainerkoenig
# Gitlab Need To Know
2
3
The [Gitlab QA SLE Functional repo](https://gitlab.suse.de/qsf-y/qa-sle-functional-y) is used to create the job group definition for SLE15 on openqa.suse.de. 
4
5
## How are the group definitions organized?
6
7
The definitons are stored under the `JobGroups` directory.
8
9
### Test suites
10
The file `test_suites.yaml` holds the test suites definitions in alphabetical order. 
11
12
Every test suite has an **anchor** that has the name of the test suite:
13
14
~~~ yaml
15
  generic_testsuite: &generic_testsuite
16
    descriptin: >-
17
      just for demonstation
18
~~~
19
20
### Job group definitions
21
22
The directory `SLE15` contains the architecture specific parts of the job groups file and the defaults.
23
24
Test suites in the `../test_suites.yaml` file are referenced with an **alias** there:
25
26
~~~ yaml
27
x86_64:
28
  sle-15-SP4-Full-x86_64:
29
    - generic_testsuite
30
        <<: *generic_testsuite
31
        settings:
32
~~~
33
34
## Fork & Merge workflow
35
36
When you want to change the definitions, you need to
37
* [fork](https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html) the repository. **Important**: After forking the repository you need to [define the variables](https://docs.gitlab.com/ee/ci/variables/) APIKEY and APISECRET and fill them with your keys for openqa.opensuse.de! The variables will be needed in the CI workflow.
38
* create a branch for your edits
39
* do the editing and commit the changes
40
* create a merge request. The merge request will trigger the CI pipeline and the test part of the pipeline relies on the variables (see above) that you need to set after forking the repository.