nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Trigger pipeline by tag, while pushing tags only

Janne Costiander

Hi,

We have set up a pipeline which is triggered by tags, and it works nicely. However, it only recognizes a tag if the tag was pushed with some commit. If you push only tags (git push --tags) with no other changes, the pipeline does not get triggered (the tag appears nicely to the latest commit)

In comparison, in Docker Cloud the automated builds are activated also with "tags only" push.

Is there a way to make this happen? I want to create the release tag when other developers have finished their work, and just release the latest commit by tagging it.

Accepted answers

Philip Hodder

Hi Janne,

Can you paste in an example of your configuration?

I got one behaving the way you want with the following configuration:

pipelines:
  branches:
    '*':
      - step:
          script:
            - echo "A branch push build"
  tags:
    release-*:
      - step:
          script:
            - echo "A tag triggered build"

The tags section will build on any pushed tags that start with "release". And does not require a new commit.

Let me know how you go.

Thanks,

Phil

All comments

Philip Hodder

Hi Janne,

Can you paste in an example of your configuration?

I got one behaving the way you want with the following configuration:

pipelines:
  branches:
    '*':
      - step:
          script:
            - echo "A branch push build"
  tags:
    release-*:
      - step:
          script:
            - echo "A tag triggered build"

The tags section will build on any pushed tags that start with "release". And does not require a new commit.

Let me know how you go.

Thanks,

Phil

Janne Costiander

Hi,

My tags-section looks like this:

tags:
  '*':
    - step:
        name: Build and test angular app
        caches:
          - node
        script:
          - npm install -g @angular/cli
          - npm install
          - ng build --target=production --no-progress
          - ng test --watch=false --no-progress
   - step:
       name: Build docker image and push to Docker hub
       script:
         - docker login -u $DOCKER_USERNAME -p $DOCKER_PASSWORD
         - docker build -t project:$BITBUCKET_TAG .
         - docker push project:$BITBUCKET_TAG
         - docker tag project:$BITBUCKET_TAG project:latest
         - docker push project:latest

But gets only triggered if there is commit also.

Janne Costiander

Hi,

My tags-section looks like this:

tags:
 '*':
 - step:
 name: Build and test angular app
 caches:
 - node
 script:
 - npm install -g @angular/cli
 - npm install
 - ng build --target=production --no-progress
 - ng test --watch=false --no-progress
 - step:
 name: Build docker image and push to Docker hub
 script:
 - docker login -u $DOCKER_USERNAME -p $DOCKER_PASSWORD
 - docker build -t project:$BITBUCKET_TAG .
 - docker push project:$BITBUCKET_TAG
 - docker tag project:$BITBUCKET_TAG project:latest
 - docker push project:latest

Philip Hodder

Hmmm...

I've set up a repo here testing this. Does this look like the correct behaviour to you? I've created multiple tags against a commit that already exists and pushed them with "git push --tags". Is that the same thing you're trying to do?

Repo: https://bitbucket.org/phodder/push-tag-test/addon/pipelines/home#!/

If there's no obvious differences between our repos, can you have a look at your repository settings for webhooks. Settings -> Workflows -> Webhooks -> Pipelines (https://bitbucket-pipelines.prod.public.atl-paas.net/rest/bitbucket/event/connect/onpush)

Do you see any failed webhooks?

Otherwise, can you try to add the following to your configuration?

pipelines:
  # keep the tag stuff
  default:
    - step:
        script:
          - echo "Hi"

Then push a new commit, and after see if tag pushes work afterwards?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket

bitbucket-cloud

bitbucket-pipelines