F5/unison
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: Update CI/CD summary with post from Natale

Browse Source
This commit is contained in:
Tom Henderson
2020-03-13 11:12:55 -07:00
parent 3a2fe9726b
commit c84fa3fb13
1 changed files with 29 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
utils/tests/README.md
View File

@@ -50,4 +50,32 @@ To perform a deeper test, you can manually run the daily or the weekly test. Go
Related to the timeout, our `gitlab-ci.yml` script also configures the job-level timeout. Currently, this timeout is set to 9h considering the extensive and time-consuming testing done in weekly jobs.
**Note**: The job-level timeout can exceed the [project-level](https://docs.gitlab.com/ce/user/project/pipelines/settings.html#timeout) timeout (default: 60 min), but can not exceed the Runner-specific timeout.
**Note**: The job-level timeout can exceed the [project-level](https://docs.gitlab.com/ce/user/project/pipelines/settings.html#timeout) timeout (default: 60 min), but can not exceed the Runner-specific timeout.
To summarize, if you are unsure about the commit you're about to
merge into master, you can push it to a branch of your fork, then go to
the Gitlab interface, click CI/CD, click Schedules, create a New
schedule, set the description, any pattern that you wish to use, and the
target branch you want to test. Then, put one or more variables from the
list below:
```shell
RELEASE, that can take the value "weekly" or "daily" or "monthly"
(if you want to perform all the build/test that are done daily, once a week,
or once a month, respectively)
FEDORA = True
(to test all the fedora builds)
UBUNTU = True
(to test all the Ubuntu builds)
GCC_BUILD_ENABLE = True
(to test all the GCC builds)
CLANG_BUILD_ENABLE = True
(to test all the clang builds)
```
... and then click Save, and run it manually from the "Schedules" page.