Name |
Last commit
|
Last update |
---|---|---|
.. | ||
api | ||
build_artifacts | ||
deployment | ||
docker | ||
examples | ||
img | ||
permissions | ||
quick_start | ||
runners | ||
services | ||
ssh_keys | ||
triggers | ||
variables | ||
yaml | ||
README.md | ||
enable_or_disable_ci.md |
BigW Consortium Gitlab
CI: Add 'triggers' keyword to 'only' and 'except' lists to allow control over when triggers cause builds to run Currently, the `only` and `except` keywords in `.gitlab-ci.yml` only accept ref names or the special `branches` and `tags` keywords. However, these are primarily useful when controlling how repository activity affects the creation of builds. In my case, instead of building on every commit, I'd like to use the following logic: - If the repository is tagged, do a build. - Any other normal commits should not cause a build. - If a build is triggered via the API, always create one for the specified ref. From what I can tell, this isn't possible via the existing YAML syntax. In this MR, I introduce a new keyword `triggers` that goes along with `branches` and `tags`. I can implement the logic above using the following job configuration: ```yaml only: - tags - triggers ``` I updated the tests and documentation to reflect this and everything seems to pass. See merge request !3230
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
api | Loading commit data... | |
build_artifacts | Loading commit data... | |
deployment | Loading commit data... | |
docker | Loading commit data... | |
examples | Loading commit data... | |
img | Loading commit data... | |
permissions | Loading commit data... | |
quick_start | Loading commit data... | |
runners | Loading commit data... | |
services | Loading commit data... | |
ssh_keys | Loading commit data... | |
triggers | Loading commit data... | |
variables | Loading commit data... | |
yaml | Loading commit data... | |
README.md | Loading commit data... | |
enable_or_disable_ci.md | Loading commit data... |