Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • network/gdev-800 protected
  • cgeek/issue-297-cpu
  • gdev-800-tests
  • update-docker-compose-rpc-squid-names
  • fix-252
  • 1000i100-test
  • hugo/tmp-0.9.1
  • network/gdev-803 protected
  • hugo/endpoint-gossip
  • network/gdev-802 protected
  • hugo/distance-precompute
  • network/gdev-900 protected
  • tuxmain/anonymous-tx
  • debug/podman
  • hugo/195-doc
  • hugo/195-graphql-schema
  • hugo-tmp-dockerfile-cache
  • release/client-800.2 protected
  • release/runtime-800 protected
  • gdev-900-0.10.1 protected
  • gdev-900-0.10.0 protected
  • gdev-900-0.9.2 protected
  • gdev-800-0.8.0 protected
  • gdev-900-0.9.1 protected
  • gdev-900-0.9.0 protected
  • gdev-803 protected
  • gdev-802 protected
  • runtime-801 protected
  • gdev-800 protected
  • runtime-800-bis protected
  • runtime-800 protected
  • runtime-800-backup protected
  • runtime-701 protected
  • runtime-700 protected
  • runtime-600 protected
  • runtime-500 protected
  • v0.4.1 protected
  • runtime-401 protected
  • v0.4.0 protected
40 results

duniter-v2s

  • Clone with SSH
  • Clone with HTTPS
    • Moul's avatar
    ci: Present docker jobs available only if based on a protected reference
    Moul authored 
    Regarding jobs:
- deploy_docker_test_image
- deploy_docker_release_sha
it doesn’t make sense to have these jobs available since
it will fail with DockerHub password missing since it’s not
running on a protected branch or tag

Brought some difficulty https://forum.duniter.org/t//10164/17

https://stackoverflow.com/questions/54901151/how-do-i-configure-gitlab-ci-jobs-to-run-on-protected-branches-only
    e8511d54
    History
    Moul's avatar e8511d54
    History
    Name Last commit Last update