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:
PYPYWEBSITEPUSHTOKEN:
@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).
@gracinet: does this look right? Do I need to add an
hg push
line as well?Yes, but you found out before I came back.
Did it work right away, then? No need to create a deploy key for that?
Right, it needs some kind of key. The CI fails with
Then you need to
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)
Not clear. Where does the public key go and where does the private key go?
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_tokensproject_80_bot
(you'll see it in the members list in case of doubt)PYPY_WEBSITE_PUSH_TOKEN
with the token (there's an option to avoid disclosing it in logs)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).
Thanks that works. The [skip ci] is important, I went to sleep without adding it and got 250 extra commits.