An error occurred while fetching the assigned milestone of the selected merge_request.
Add canary deploys
3 unresolved threads
3 unresolved threads
The auto-deploy changes will be linked.
Merge request reports
Activity
32 when: manual 33 allow_failure: false 34 only: 35 - master 36 24 37 production: 25 38 stage: production 26 variables: 27 CI_ENVIRONMENT_URL: http://$CI_PROJECT_NAME.$KUBE_DOMAIN 28 39 script: 29 40 - command deploy 30 41 environment: 31 42 name: production 32 43 url: http://$CI_PROJECT_NAME.$KUBE_DOMAIN 33 44 when: manual 45 allow_failure: false @zj Manual jobs default to
allow_failure: true, iirc
21 22 only: 22 23 - branches 23 24 25 canary: @ayufan This makes canaries part of every auto deploy, even for GitLab CE. Are we sure we want to do that? Can we have a different template for CE vs EE? I mean, it's not horrible to do it this way. But it means we're giving some level of canary deploy support to CE, and only visualization of canary deploys to EEP. /cc @JobV
71 79 name: review/$CI_COMMIT_REF_NAME @ayufan Shouldn't this be
CI_COMMIT_REF_SLUG?
mentioned in merge request !70 (merged)
Please register or sign in to reply