add a gitlab-ci runner
Fixes to #9
Merge request reports
Activity
mentioned in issue #9
- .gitlab-ci.yml 0 → 100644
12 # image: registry.heptapod.net/octobus/ci-dockerfiles/ci-website 13 # stage: deploy 14 # script: 15 # - make build # use artefact eventually 16 # - netlify deploy --site=056ee9b4-122d-4b02-bf62-5a2fc9776196 --auth="$NETLIFY_AUTH_TOKEN" --dir="public" 17 18 deploy: 19 # On a merge, regenerate the content and commit it to the repo 20 image: registry.heptapod.net/pypy/pypy/ci:v1 21 stage: deploy 22 only: 23 - branch/default 24 script: 25 - make build 26 - hg add public 27 - hg commit public @gracinet: does this look right? Do I need to add an
hg push
line as well?Right, it needs some kind of key. The CI fails with
abort: http authorization required for https://foss.heptapod.net/pypy/pypy.org
Then you need to
- create a (SSH) deploy key with write permission: https://foss.heptapod.net/help/user/project/deploy_keys/index.md
- Give it to the pipelines for this project as a 'file' variable
- push over SSH using that key (either using
hg --ssh 'ssh -i the-key
or by preparing a.ssh/config
)
See also https://foss.heptapod.net/help/ci/ssh_keys/README.md
Optionally, if you don't want a new pipeline to be triggered by that push, you can include
[skip ci]
in the first line of the commit message.(I thought that deploy tokens could have write permissions, but it's apparently only to push to the Docker and Package registries)
The private key goes to pipeline variables, but forget about it, seems I read the doc too fast.
Try adding a project access token with
write_repository
scope instead: https://foss.heptapod.net/pypy/pypy.org/-/settings/access_tokens- save the token immediately, it's only displayed once
- the corresponding user name should be
project_80_bot
(you'll see it in the members list in case of doubt) - define a pipeline variable
PYPY_WEBSITE_PUSH_TOKEN
with the token (there's an option to avoid disclosing it in logs) - push to https://project_80_bo:{PYPY_WEBSITE_PUSH_TOKEN}:@foss.heptapod.net
Bottom line, write deploy tokens seem to exist after all, I haven't yet, but if it doesn't work, that's a bug I will fix for 0.18.1 and/or 0.19.0 final).
mentioned in commit 6755ce52d95d