diff options
| author | Varac <varac@leap.se> | 2017-06-26 21:31:07 +0200 |
|---|---|---|
| committer | Varac <varac@leap.se> | 2017-06-26 21:31:07 +0200 |
| commit | e24292f13a6bef60ee7b8f2aa0ac2174ad96397e (patch) | |
| tree | 463cb6c4774a9a0cef4770923def06c8803415c1 | |
| parent | 1c00a62a89301866cd68900e25e1a45a108f67d4 (diff) | |
Add manual deploy test for master branch
| -rw-r--r-- | .gitlab-ci.yml | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index c4de7086..21ea1f73 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -64,6 +64,17 @@ deploy_test: script: - su -c 'set -o pipefail; stdbuf -oL -eL ./ci-build.sh | ts' cirunner +# However, sometimes it's important to have a way of triggering a deploy +# from scratch manually even from the master branch, when i.e. new packages +# got uploaded to the master component of the platform deb repo. +deploy_test:manual: + stage: deploy + only: + - master + when: manual + script: + - su -c 'set -o pipefail; stdbuf -oL -eL ./ci-build.sh | ts' cirunner + # Latest job will only run on the master branch, which means all merge requests # that are created from branches don't get to deploy to the latest-ci server. # When a merge request is merged, then the latest job will deploy the code to |