summaryrefslogtreecommitdiffstats
path: root/package/python-setuptools
diff options
context:
space:
mode:
authorRicardo Martincoski <ricardo.martincoski@gmail.com>2018-10-28 20:58:37 -0300
committerArnout Vandecappelle (Essensium/Mind) <arnout@mind.be>2018-11-14 09:18:40 +0100
commitf177fd66e47879a72bb678a2de7ce658410cc4b9 (patch)
tree30d7f98d637f4ba8ade9cc6b61fc67387c9b0099 /package/python-setuptools
parent3db2ed427138ff0e20aebcac3f40e5b90a749d08 (diff)
downloadbuildroot-f177fd66e47879a72bb678a2de7ce658410cc4b9.tar.gz
buildroot-f177fd66e47879a72bb678a2de7ce658410cc4b9.zip
.gitlab-ci.yml: add trigger per type of job
Currently the user has 2 sets of jobs that can be triggered on a GitLab pipeline. - to trigger all defconfigs, all runtime tests and all check-* jobs: $ git tag <name> $ git push gitlab <name> # currently 260 jobs - to trigger only the check-* jobs: $ git push gitlab HEAD:<name> # currently 4 jobs This is not much versatile, so the user ends up hand-editing the .gitlab-ci.yml in order to trigger some subsets, even the common ones, for instance all runtime tests. Add 2 more subsets that can be triggered based on the name of the branch pushed. - to trigger all defconfigs and all check-* jobs: $ git push gitlab HEAD:<name>-defconfigs # currently 192 jobs - to trigger all runtime tests and all check-* jobs: $ git push gitlab HEAD:<name>-runtime-tests # currently 72 jobs Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Diffstat (limited to 'package/python-setuptools')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud