Need to fix GitLab CI for Duniter-v2s

Nodes Duniter-v2s
21

Ok, thanks for finding out! I think @Pini did set these variables in his own repo to be able to upload to his dockerhub space, but the variables are not defined in the main repo.

I thing it is ok to keep these variables, but we have to document the CI. @Pini can you submit a MR documenting all the variables that have to be set in order to be able to use the CI? @Moul it would also be interesting to have a small paragraph summarizing the security rules of the pipeline (like release CI requirements).

I will add the missing variables REPO_DOCKER_USER and REPO_DOCKER_PASS in the main docker to be able tu publish an official release docker image for the new smiths to join.

22

GitLab documentation already contains it:

I let you add it to Duniter-v2s documentation.

1 Like
23

Sorry, all this is my fault: a while ago I accidentally pushed to this branch some commits I did to test the CI on my own fork. I didn’t clean up since I thought I was the only user of this now deprecated branch.

You don’t need to. These variables are not the ones used by the CI. Please see the .gitlab-ci.yml file on the master branch. To release you’ll only need the protected variable DUNITERTEAM_PASSWORD already defined in the repository settings.

1 Like
24

Ok, thank you both. I appreciate your answers, it allows me to understand without having to dig.

The documentation I imagine would be something like:

duniter-v2s repo has protected tags and branches (see here). To see how this work see

The protected tags are: runtime-*, v*
The protected branches are: master and release/*

These branches and tags give access to DUNITERTEAM_PASSWD variable allowing to push images to dockerhub.

That’s enough, but that’s what was missing for me when I published (DifficultĂ©s avec l'outillage). I had no clue about docker, gitlab, ci
 That does not prevent me from contributing to Duniter because I know Rust and Substrate, but that makes everything difficult. I have no whish to learn that, I only want to learn Duniter as fast as I can. So thanks again for being here ^^

25

After adding the required variables, the CI fails with:

Error parsing reference: "/duniter-v2s:sha-3189d769" is not a valid repository/tag: invalid reference format

It seems @Pini that there is still some problems in this version of the CI.
Since the goal is to provide future smith an official docker image with the good chainspec, maybe we can create a new branch based on the newer Duniter client (and with all the docker improvements), with the chainspec commits, test if it connects well to the ĞDev network, and then propose a runtime upgrade on this network with the recent updates.

So instead of fixing CI for this old branch, only cherry-pick chainspec commits on an other branch.

26

I did launch again this job with the good variables, and now, it stops at a more interesting-looking error:

ERROR: Job failed (system failure): Error response from daemon: Cannot link to a non running container: /runner-yx9a3lzn-project-520-concurrent-0-7096a3feb2e9539c-docker-0 AS /runner-yx9a3lzn-project-520-concurrent-0-7096a3feb2e9539c-build-3/docker (exec.go:78:0s)

A bug with the gitlab-runner?

27

3 posts were split to a new topic: Release new image with ĞDev5 chainspecs