Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,548
Community Members
 
Community Events
176
Community Groups

Creating a tag during build does not trigger the tag pipeline

Creating a tag during build does not trigger the tag pipeline

I do use semantic-release in on my master

as per my bitbucket-pipelines.yml I added a tags section for build (which can be triggered when the tag is created manually)

I would like that my semantic-release trigger the second pipeline.

Any ideas ? 

1 answer

1 vote

Hi @Meher Gara,

I assume that you don't have a command to create a tag in the bitbucket-pipelines.yml file, but the tag is created by semantic-release?

I suggest checking two things first:

1) After the tag gets created, does the Pipelines build push back to the Bitbucket repo?

When a Pipelines build runs on a certain branch, then a Docker container starts, this specific branch of the Bitbucket repo gets cloned inside the Docker container and then the script of the yaml file runs.

If a tag gets created during the build, it will get created in the clone of the repo inside the Docker container, and not in the Bitbucket repo.

I am not familiar with semantic-release and I'm not sure if it can be configured to push tags to the Bitbucket repo.

However, you can add the following command in your bitbucket-pipelines.yml file, in the script of the step where the tag gets created (after the command that creates the tag), and the tag will get pushed to the Bitbucket repo:

git push origin --tags

2) Assuming that the tag gets created by semantic-release, do the tag names follow a certain pattern?

And does that pattern match the pattern you specified in the tags definition in the bitbucket-pipelines.yml file?

Kind regards,
Theodora

Indeed the tag is created but it's not pushed.

Thanks for the support ! 

Like # people like this

You are very welcome, I'm glad to have helped!

Please feel free to reach out if you ever need anything else.

Kind regards,
Theodora

Like Vyacheslav Zgordan likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events