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

utils: (fixes #138) Update CI scripts and README file after adding timeout value

Browse Source 
see merge request !187
This commit is contained in:
Eduardo Almeida
2020-02-12 16:21:15 +00:00
committed by ZorazeAli
parent 29d5ce4053
commit 153492e56d
2 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
utils/tests/README.md
View File

@@ -36,6 +36,7 @@ Thanks to the "Schedule" feature of Gitlab, we setup pipelines that have to be r
As weekly jobs, we perform the build, testing, and documentation stage in every platform we support (Ubuntu, Fedora, Arch Linux) with all the compilers we support (GCC and CLang). Weekly pipelines should define a variable, named `RELEASE`, as `weekly`. To add the support for your platform, please see how the jobs are constructed (for instance, the GCC jobs are in `gitlab-ci-gcc.yml`). We currently miss the jobs for OS X and Windows.
## Test your changes
When you fork ns-3-dev on Gitlab, you get access to 2000 free hours of execution time on the Gitlab CI infrastructure. You automatically inherit all the scripts as well, so you can test your changes before requesting a merge. As mentioned previously, we store our YML files under the directory ./utils/tests, therefore, to execute per-commit script automatically, Gitlab CI/CD requires a custom path to the YML file.
To customize the path:
@@ -46,3 +47,7 @@ To customize the path:
4. Click **Save changes**.
To perform a deeper test, you can manually run the daily or the weekly test. Go to the Gitlab interface, then enter in the CI/CD menu and select Pipelines. On the top, you can manually run a pipeline: select the branch, and add a variable `RELEASE` set to `daily` or `weekly` following your need, and then run it.
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.

1
utils/tests/gitlab-ci.yml
View File

@@ -42,6 +42,7 @@ stages:
cache:
paths:
- $CCACHE_BASEDIR_VALUE/
timeout: 9h
variables:
CCACHE_BASEDIR_VALUE: ns-3-ccache-storage