Push Dockerhub README.md file on release

Add stage 'readme' and job 'readme_docker_release_tag' to push the file 'docker/README.md' to the team's duniter-v2s repo.

The job uses chko/docker-pushrm and is adapted from the related Gitlab CI/CD example.

See https://github.com/christian-korneck/docker-pushrm

assigned to @pini-gh

@HugoTrentesaux

This is a work in progress MR on top of the previous one (branch 'pini-docker').

I've just copy/pasted and adapted the docker-pushrm Gitlab CI/CD example. The job runs only on versioned release because - IMHO - the README should match the current latest image.

But I don't know how to test it. Could you ping someone in the team knowledgeable in Gitlab CI/CD to review this proposal?

BTW this MR also adds 'sha-latest' Docker tag on sha release.

added 1 commit

• fa764ade - ci: rename stage readme to deploy_readme

Compare with previous version

PS : i don't know how to test docker publish without really publishing. If you want to test it anywhere else than duniter/duniter-v2s, probably a pini/duniter-publish-test could do the job.

added 1 commit

• 2442675e - ci: deploy_readme: fix target path

Compare with previous version

resolved all threads

It works See: https://hub.docker.com/repository/docker/pinidh/duniter-v2s/general

Note: I had to change the rule on my repo to trigger the job manually. I guess this is not wanted here because the README should be updated on official release only.

added 2 commits

• 254f2a33 - ci: use anonymized variables for dockerhub
• 903cedc4 - ci: trigger readme_docker_release_tag manually

Compare with previous version

added 7 commits

• 236a4a4c - 1 commit from branch pini-docker
• 119f7d71 - ci: docker tag 'sha-latest'
• 2d6dfe87 - docker: push README.md on release
• 02d97bbf - ci: rename stage readme to deploy_readme
• 6de50f44 - ci: deploy_readme: fix target path
• 6c8d7b80 - ci: use anonymized variables for dockerhub
• 3189d769 - ci: trigger readme_docker_release_tag manually

Compare with previous version

added 20 commits

• 3189d769...bae38a79 - 15 commits from branch pini-docker
• b22e832b - docker: document docker image usage with README.md
• 31a0c351 - ci: docker tag 'sha-latest'
• a0e261df - docker: push README.md on release
• 4b0e4d57 - ci: rename stage readme to deploy_readme
• d0013312 - ci: deploy_readme: fix target path

Compare with previous version

deleted the pini-docker branch. This merge request now targets the master branch

added 3 commits

• 585d5807 - 1 commit from branch master
• 54bc0115 - ci: docker tag 'sha-latest'
• 8cc65515 - docker: push README.md on release

Compare with previous version

marked this merge request as ready

added C-cicd label

added RN-silent label

added 1 commit

• 41d37d19 - docker: push README.md on release

Compare with previous version

changed title from Docker tag sha-latest and push Dockerhub README.md file on release to Push Dockerhub README.md file on release

changed the description

I finally dropped the commit ci: docker tag 'sha-latest' because I understand now that we don't want to tag sha-latest each time we deploy an sha release.

added 3 commits

• 41d37d19...dacbfa8f - 2 commits from branch master
• 56b7b2e6 - docker: push README.md on release

Compare with previous version

added 2 commits

• 44c22c2a - 1 commit from branch master
• a3b53828 - docker: push README.md on release

Compare with previous version

added 5 commits

• a3b53828...3aca4ecd - 4 commits from branch master
• 67a84f95 - docker: push README.md on release

Compare with previous version

added 5 commits

• 67a84f95...cee8975b - 4 commits from branch master
• e063a6fd - docker: push README.md on release

Compare with previous version

merged