Mirrored_Repos/veloren
1
0
Fork 0
mirror of https://gitlab.com/veloren/veloren.git synced 2024-08-30 18:12:32 +00:00
Code Issues Packages Projects Releases Wiki Activity
64f6faece5
veloren/.gitlab/CI/publish.gitlab-ci.yml

74 lines
2.7 KiB
YAML
Raw Normal View History

change(ci): adjust docs + fix release template
2020-05-23 08:02:39 +00:00
# Publishes veloren-server-cli to the gitlab container registry
# https://gitlab.com/veloren/veloren/container_registry
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
.publish:
change(ci): document and add retries + fmt
2020-05-14 16:12:22 +00:00
stage: publish
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:
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_BRANCH == $CI_DEFAULT_BRANCH && $CI_PIPELINE_SOURCE != "schedule"
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
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
.publish-nightly:
stage: publish
rules:
make sure that all CI jobs run always and not only in branch
2021-06-28 19:22:59 +00:00
- if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH && $CI_PIPELINE_SOURCE == "schedule"
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
first rule evaluated to never, switched that
2020-06-17 08:41:05 +00:00
- 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
docker:
extends: .publish
change(ci): document and add retries + fmt
2020-05-14 16:12:22 +00:00
image:
name: gcr.io/kaniko-project/executor:debug
entrypoint: [""]
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", "publish", "trusted"]
change(ci): document and add retries + fmt
2020-05-14 16:12:22 +00:00
dependencies:
- linux
before_script:
- ls "$CI_PROJECT_DIR/server-cli/"
script:
quickfix to avoid kaniko stopping with "kaniko should only be run inside of a container, run with the --force flag if you are sure you want to continue" error applied as described here https://github.com/GoogleContainerTools/kaniko/issues/1542 its also done in veloren-docker-cli: https://gitlab.com/veloren/veloren-docker-ci/-/commit/c8aa8ac857292cf28e37dfd009c96c43ab02d206?merge_request_iid=50 We didnt had that problem in veloren repo until now.
2021-07-19 11:33:19 +00:00
# Help kaniko identify that it is running in a container.
# avoids this issue: https://github.com/GoogleContainerTools/kaniko/issues/1542
- export container=docker
change(ci): document and add retries + fmt
2020-05-14 16:12:22 +00:00
- echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json
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
- /kaniko/executor --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/server-cli/Dockerfile --destination "${CI_REGISTRY_IMAGE}/server-cli:${CI_COMMIT_REF_NAME}"
docker-nightly:
extends: .publish-nightly
image:
name: gcr.io/kaniko-project/executor:debug
entrypoint: [""]
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", "publish", "trusted"]
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
dependencies:
Make docker-nightly job depend on the nightly air-linux job
2021-06-04 07:24:57 +00:00
- air-linux
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
before_script:
- ls "$CI_PROJECT_DIR/server-cli/"
script:
quickfix to avoid kaniko stopping with "kaniko should only be run inside of a container, run with the --force flag if you are sure you want to continue" error applied as described here https://github.com/GoogleContainerTools/kaniko/issues/1542 its also done in veloren-docker-cli: https://gitlab.com/veloren/veloren-docker-ci/-/commit/c8aa8ac857292cf28e37dfd009c96c43ab02d206?merge_request_iid=50 We didnt had that problem in veloren repo until now.
2021-07-19 11:33:19 +00:00
# Help kaniko identify that it is running in a container.
# avoids this issue: https://github.com/GoogleContainerTools/kaniko/issues/1542
- export container=docker
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
- echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json
- /kaniko/executor --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/server-cli/Dockerfile --destination "${CI_REGISTRY_IMAGE}/server-cli:nightly"
Test pages Added stage Move files to public Move folder instead Make if already exists Move filees Finished cleaning
2020-06-11 13:24:07 +00:00
create a nightly tag that always point to the released nightly version of veloren in the respective schedule so that others can consume it
2021-07-20 21:03:10 +00:00
tag-nightly:
extends: .publish-nightly
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", "publish", "trusted"]
create a nightly tag that always point to the released nightly version of veloren in the respective schedule so that others can consume it
2021-07-20 21:03:10 +00:00
script:
- git config --global user.email "gitlab-veloren-bot@veloren.net"
- git config --global user.name "veloren-bot"
- git config --global http.postBuffer 52428800
- git remote set-url origin https://veloren-bot:${GITLAB_TOKEN_WRITE}@${CI_PROJECT_URL:8}
- git tag -a "nightly" -m '' -f
- git push origin nightly -f
Test pages Added stage Move files to public Move folder instead Make if already exists Move filees Finished cleaning
2020-06-11 13:24:07 +00:00
pages:
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
extends: .publish
Fix pages by specifying a docker image
2021-06-01 20:26:41 +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", "publish"]
Test pages Added stage Move files to public Move folder instead Make if already exists Move filees Finished cleaning
2020-06-11 13:24:07 +00:00
artifacts:
paths:
fix(ci): pages document default features only related to !1094
2020-06-19 07:39:53 +00:00
- public
Test pages Added stage Move files to public Move folder instead Make if already exists Move filees Finished cleaning
2020-06-11 13:24:07 +00:00
script:
- rm -rf public
- mkdir -p public
partially fix pages
2020-09-17 10:03:50 +00:00
- cargo doc --no-deps --document-private-items
create a nightly tag that always point to the released nightly version of veloren in the respective schedule so that others can consume it
2021-07-20 21:03:10 +00:00
- mv target/doc/* public
Reference in New Issue Copy Permalink