Skipping a deployment with the script provider because this branch is not permitted: advanced-1.0.0


#1

I tried to push the tag to the master branch. But the deploy is not being executed correctly
https://travis-ci.org/kubesphere/devops/builds/454893079

language: go

go_import_path: kubesphere.io/devops

go:
  - "1.10.3"

sudo: required

services:
- docker

before_script:
- docker --version

install:
  - chmod +x hack/*.sh
  - go get golang.org/x/tools/cmd/goimports

scripts:
  - make check
  - make test

deploy:
  - provider: script
    script: bash hack/docker_push.sh latest
    on:
      branch: master
      repo: kubesphere/devops
  - provider: script
    script: bash hack/docker_push.sh $TRAVIS_TAG
    on:
      tags: true
      repo: kubesphere/devops


#2

Please elaborate on what you mean by “not being executed correctly”. I see that the deployment is correctly initiated.


#3

Deploy is not executed when I push tag to the master branch


#4

I’m sorry, but I must be missing something, because https://travis-ci.org/kubesphere/devops/builds/454893079#L490 shows that the deployment is triggered on the advanced-1.0.0 tag.

(As an aside, note that a git tag is tied to a commit, not a branch, so “push tag to the master branch” is semantically incorrect.)


#5

Many thanks to the reminder about the tag statement error. In my travis yaml, the “deploy step” is included, and this step does not have a normal trigger in this build. Output log prompt

Skipping a deployment with the script provider because this branch is not permitted: advanced-1.0.0

#6

Thanks for the clarification. You have two deployment providers defined. One that acts on branch: master, and the other on tags: true. The “not started” message comes from the first, as this is a tag build (and not a master branch build).


#7

So what if I want to execute different deploys in the tagged version? In the https://travis-ci.org/openpitrix/openpitrix/jobs/454336818#L3100 repository, the yaml file can be written in the same way to execute the tag deploy. Did I make a mistake?


#8

You can define multiple deployment providers acting on the same condition.