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
  rules:
    - if: $CI_PIPELINE_SOURCE != "merge_request_event" || $CI_PIPELINE_SOURCE == "schedule" || ( $CI_COMMIT_TAG != null && $CI_COMMIT_TAG =~ $TAG_REGEX )
      when: never
    - when: manual
      allow_failure: true

# Template to only run if pushes to master, schedule or a version tag
.release:
  stage: build
  rules:
    - if: $CI_PIPELINE_SOURCE != "merge_request_event" && ( $CI_PIPELINE_SOURCE == "schedule" || $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH || ( $CI_COMMIT_TAG != null && $CI_COMMIT_TAG =~ $TAG_REGEX ) )
      when: on_success
    - when: never
  retry:
    max: 1
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			`rules:`
simply scripts alot, not the null check is necessray because gitlab ci regex with variables is weird and would contain errors otherwise. limit pages to master run only, as we dont export scheduled pages 2022-04-06 19:08:29 +00:00			`- if: $CI_PIPELINE_SOURCE != "merge_request_event" \|\| $CI_PIPELINE_SOURCE == "schedule" \|\| ( $CI_COMMIT_TAG != null && $CI_COMMIT_TAG =~ $TAG_REGEX )`
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: 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
remove duplicate airshipper ci jobs. Introduce weekly build. This requires the veloren schedule to contain variables and requires the airshipper server to handle those in the config 2022-03-19 11:49:40 +00:00			`# Template to only run if pushes to master, schedule or a version tag`
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`
change(ci): centralise master/tag push check 2020-05-18 17:32:21 +00:00			`rules:`
simply scripts alot, not the null check is necessray because gitlab ci regex with variables is weird and would contain errors otherwise. limit pages to master run only, as we dont export scheduled pages 2022-04-06 19:08:29 +00:00			`- if: $CI_PIPELINE_SOURCE != "merge_request_event" && ( $CI_PIPELINE_SOURCE == "schedule" \|\| $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH \|\| ( $CI_COMMIT_TAG != null && $CI_COMMIT_TAG =~ $TAG_REGEX ) )`
execute jobs only if all previous jobs in previous stages succeded, e.g. in case of error in windows job dont push the linux docker container or change the tag yet 2021-07-22 10:05:30 +00:00			`when: on_success`
have a seperate stage for scheduled builds 2021-04-23 15:47:55 +00:00			`- when: never`
Retry release jobs on failure 2021-07-30 22:09:54 +00:00			`retry:`
remove duplicate airshipper ci jobs. Introduce weekly build. This requires the veloren schedule to contain variables and requires the airshipper server to handle those in the config 2022-03-19 11:49:40 +00:00			`max: 1`