From bd60189bf8f3c09a995e2b2891660667955808ff Mon Sep 17 00:00:00 2001 From: Justin Kromlinger Date: Thu, 13 Jun 2024 13:13:54 +0200 Subject: [PATCH] Add documentation about `GITLAB_PROJECT_TOKEN` --- .gitlab-ci.yml | 1 + README.md | 6 ++++++ 2 files changed, 7 insertions(+) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index f33857d..c35da28 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -248,6 +248,7 @@ pre-release: ./scripts/make-dockerfile.sh "${rootfs_file}" "${group}" "output" "curl -sOJL \"${PACKAGE_REGISTRY_URL}/${rootfs_file}\"" "${group}" sed -i "/^COPY ${rootfs_file} \/$/d" output/Dockerfile.${group} done + # See README.md###Maintenance for notes about `GITLAB_PROJECT_TOKEN` - > curl -sSf --request POST -o commit-response.json --header "PRIVATE-TOKEN: ${GITLAB_PROJECT_TOKEN}" diff --git a/README.md b/README.md index 65f51fe..928a6b9 100644 --- a/README.md +++ b/README.md @@ -94,6 +94,10 @@ Changes in Git feature branches are built and tested using the pipeline as well. Development images are uploaded to our [GitLab Container Registry][self-container-registry]. +### Maintenance + +Every year in June the content of the protected `GITLAB_PROJECT_TOKEN` variable needs to be replaced. To do this a GitLab admin needs to create a new [Access Token][access-tokens] with `api` and `write_repository` scope and the `Maintainer` role. This will create a new Bot User which needs to be given access to the protected `releases` branch. + [pipeline]: https://gitlab.archlinux.org/archlinux/archlinux-docker/badges/master/pipeline.svg [commits]: https://gitlab.archlinux.org/archlinux/archlinux-docker/-/commits/master @@ -113,3 +117,5 @@ Development images are uploaded to our [github-docker-arch]: https://github.com/docker-library/official-images/blob/master/library/archlinux [self-container-registry]: https://gitlab.archlinux.org/archlinux/archlinux-docker/container_registry + +[access-tokens]: https://gitlab.archlinux.org/archlinux/archlinux-docker/-/settings/access_tokens \ No newline at end of file