veloren/.gitlab/CI/check.gitlab-ci.yml

# cargo clippy is a superset of cargo check, so we don't check manually
code-quality:
  extends: .recompile-branch
  stage: check
  image: registry.gitlab.com/veloren/veloren-docker-ci/cache/quality:${CACHE_IMAGE_TAG}
  tags: ["veloren/veloren", "check"]
  script:
    - ln -s /dockercache/target target
    - cat ./.gitlab/scripts/code-quality.sh
    - source ./.gitlab/scripts/code-quality.sh

security:
  extends: .recompile-branch
  stage: check
  image: registry.gitlab.com/veloren/veloren-docker-ci/cache/quality:${CACHE_IMAGE_TAG}
  tags: ["veloren/veloren", "check"]
  allow_failure: true
  script:
    - ln -s /dockercache/target target
    - cat ./.gitlab/scripts/security.sh
    - source ./.gitlab/scripts/security.sh
fix ci, which was broken by merging unittests and check 2021-01-23 22:05:24 +00:00			`# cargo clippy is a superset of cargo check, so we don't check manually`
			`code-quality:`
change(ci): run coverage on branch and master 2020-06-03 08:31:05 +00:00			`extends: .recompile-branch`
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: check`
Use new multi image cache scheme in the CI and consolidate runner tag specification so that it is easier to modify 2021-05-20 04:21:53 +00:00			`image: registry.gitlab.com/veloren/veloren-docker-ci/cache/quality:${CACHE_IMAGE_TAG}`
implement a new tag system for all veloren runners, including - project tag: - `veloren/veloren`: for the veloren repo only - `veloren/`: for projects thats are in the veloren namespace, e.g. usefull for smaller projects that dont have their own tag - `/` for projects by 3rd parties, e.g. personal projects - trusted tag: - `owned`: The runner is hosted on veloren hardware - `trusted`: The runner is hosted by a private person, trusted by the veloren devs - NONE: if no special trust is given in a runner - check/build tag: - `check`: a job only performs a check and NO executable is build for users - `build`: the job contains atleast 1 executable that can be run by users - NONE: neither a check nor a executable is build, e.g. usefull for pages or meta jobs - publish tag: - `publish`: this job produces a artifact that is automatically pushed to users - NONE: no artifact is pushed automatically to users - pin tags: - `benchmark`: pin a runner to a specific job for the cause of benchmarks - `veloren/:macos`: runs on a native macos runner ONLY, this needs to be a modified project tag, as otherwise also normal checks would run on this runner. - NONE: no runner is pinned 2021-08-17 11:22:18 +00:00			`tags: ["veloren/veloren", "check"]`
change(ci): document and add retries + fmt 2020-05-14 16:12:22 +00:00			`script:`
Use new multi image cache scheme in the CI and consolidate runner tag specification so that it is easier to modify 2021-05-20 04:21:53 +00:00			`- ln -s /dockercache/target target`
extract relevant code in a script in order to remove duplicate coding with docker-ci repo export VELOREN_ASSETS without pwd to keep caching working 2021-07-14 08:25:29 +00:00			`- cat ./.gitlab/scripts/code-quality.sh`
			`- source ./.gitlab/scripts/code-quality.sh`
change(ci): split up stages into separate files 2020-05-14 15:37:34 +00:00
			`security:`
change(ci): run coverage on branch and master 2020-06-03 08:31:05 +00:00			`extends: .recompile-branch`
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: check`
Use new multi image cache scheme in the CI and consolidate runner tag specification so that it is easier to modify 2021-05-20 04:21:53 +00:00			`image: registry.gitlab.com/veloren/veloren-docker-ci/cache/quality:${CACHE_IMAGE_TAG}`
implement a new tag system for all veloren runners, including - project tag: - `veloren/veloren`: for the veloren repo only - `veloren/`: for projects thats are in the veloren namespace, e.g. usefull for smaller projects that dont have their own tag - `/` for projects by 3rd parties, e.g. personal projects - trusted tag: - `owned`: The runner is hosted on veloren hardware - `trusted`: The runner is hosted by a private person, trusted by the veloren devs - NONE: if no special trust is given in a runner - check/build tag: - `check`: a job only performs a check and NO executable is build for users - `build`: the job contains atleast 1 executable that can be run by users - NONE: neither a check nor a executable is build, e.g. usefull for pages or meta jobs - publish tag: - `publish`: this job produces a artifact that is automatically pushed to users - NONE: no artifact is pushed automatically to users - pin tags: - `benchmark`: pin a runner to a specific job for the cause of benchmarks - `veloren/:macos`: runs on a native macos runner ONLY, this needs to be a modified project tag, as otherwise also normal checks would run on this runner. - NONE: no runner is pinned 2021-08-17 11:22:18 +00:00			`tags: ["veloren/veloren", "check"]`
change(ci): document and add retries + fmt 2020-05-14 16:12:22 +00:00			`allow_failure: true`
			`script:`
Use new multi image cache scheme in the CI and consolidate runner tag specification so that it is easier to modify 2021-05-20 04:21:53 +00:00			`- ln -s /dockercache/target target`
extract relevant code in a script in order to remove duplicate coding with docker-ci repo export VELOREN_ASSETS without pwd to keep caching working 2021-07-14 08:25:29 +00:00			`- cat ./.gitlab/scripts/security.sh`
			`- source ./.gitlab/scripts/security.sh`