veloren/.gitlab/CI/release.yml

# allow_failure: true makes these pipelines manual and "non-blocking" which changed with except -> rule syntax
.optional-release:
  stage: check
  tags:
    - veloren-docker
  rules:
    - if: $CI_COMMIT_REF_NAME =~ /^master$/ || $CI_COMMIT_TAG =~ /^v[0-9]+\.[0-9]+\.[0-9]+/ || $CI_COMMIT_REF_NAME =~ /^r[0-9]+\.[0-9]+/ || $CI_PIPELINE_SOURCE == "schedule"
      when: never
    - when: manual
      allow_failure: true

# Template to only run if pushes to master or a tag happened
.release:
  stage: build
  tags:
    - veloren-docker
  rules:
    - if: $CI_COMMIT_REF_NAME =~ /^master$/ || $CI_COMMIT_TAG =~ /^v[0-9]+\.[0-9]+\.[0-9]+/ || $CI_COMMIT_REF_NAME =~ /^r[0-9]+\.[0-9]+/
      when: always
    - when: never
CI cleanup - switching more to rules syntax - clean up some templates - EITHER optional builds or build builds - ordering 2020-06-12 11:09:56 +00:00			`# allow_failure: true makes these pipelines manual and "non-blocking" which changed with except -> rule syntax`
			`.optional-release:`
put optional builds in check like imbris suggested in order to test macOS and other builds easily 2020-07-17 10:17:34 +00:00			`stage: check`
CI cleanup - switching more to rules syntax - clean up some templates - EITHER optional builds or build builds - ordering 2020-06-12 11:09:56 +00:00			`tags:`
			`- veloren-docker`
			`rules:`
			`- if: $CI_COMMIT_REF_NAME =~ /^master$/ \|\| $CI_COMMIT_TAG =~ /^v[0-9]+\.[0-9]+\.[0-9]+/ \|\| $CI_COMMIT_REF_NAME =~ /^r[0-9]+\.[0-9]+/ \|\| $CI_PIPELINE_SOURCE == "schedule"`
			`when: never`
first rule evaluated to never, switched that 2020-06-17 08:41:05 +00:00			`- when: manual`
			`allow_failure: true`
CI cleanup - switching more to rules syntax - clean up some templates - EITHER optional builds or build builds - ordering 2020-06-12 11:09:56 +00:00
use different docker tags for master and nightly runs, This allow us to decouple our test-ci from the release-ci and is necessary for multiple release channels in the future. E.g. we can run a master build without it directly beeing pushed to watchtower and airshipper (config setting requiered on airshipper) Adjust Tags for server-cli 2021-04-01 07:33:05 +00:00			`# Template to only run if pushes to master or a tag happened`
change(ci): centralise master/tag push check 2020-05-18 17:32:21 +00:00			`.release:`
CI cleanup - switching more to rules syntax - clean up some templates - EITHER optional builds or build builds - ordering 2020-06-12 11:09:56 +00:00			`stage: build`
			`tags:`
			`- veloren-docker`
change(ci): centralise master/tag push check 2020-05-18 17:32:21 +00:00			`rules:`
use different docker tags for master and nightly runs, This allow us to decouple our test-ci from the release-ci and is necessary for multiple release channels in the future. E.g. we can run a master build without it directly beeing pushed to watchtower and airshipper (config setting requiered on airshipper) Adjust Tags for server-cli 2021-04-01 07:33:05 +00:00			`- if: $CI_COMMIT_REF_NAME =~ /^master$/ \|\| $CI_COMMIT_TAG =~ /^v[0-9]+\.[0-9]+\.[0-9]+/ \|\| $CI_COMMIT_REF_NAME =~ /^r[0-9]+\.[0-9]+/`
CI cleanup - switching more to rules syntax - clean up some templates - EITHER optional builds or build builds - ordering 2020-06-12 11:09:56 +00:00			`when: always`
use different docker tags for master and nightly runs, This allow us to decouple our test-ci from the release-ci and is necessary for multiple release channels in the future. E.g. we can run a master build without it directly beeing pushed to watchtower and airshipper (config setting requiered on airshipper) Adjust Tags for server-cli 2021-04-01 07:33:05 +00:00			`- when: never`