I have noticed that Auto tags are getting created on release branch "release/v2.3.0-10_24". The issue is that the tag name is always same as branch name which causes issues while taking a pull and other tasks.
This is the only branch we have noticed this happening for now. Please let me know if any further details are needed.
FYI : there had been 3-4 incidents where I have seen this issue, and I had to explicitly delete the tag created.
Hi @Sonam_Moga1 and welcome to the community!
Bitbucket does not automatically add tags to a repo's commits.
Are you using Bitbucket Pipelines or another third-party CI/CD tool to run builds? If so, can you check the builds running for this release branch and see if these builds create a tag and then push it to the Bitbucket repo?
Kind regards,
Theodora
I'm suing Azure DevOps for CI/CD, there had been no changes in the pipelines (yml wise) and no new pipeline has been added. This issue started from almost 2 months ago.
I'm the only one who creates Tags(using a particular naming convention) for teams, now i can see that even today there was a Tag created with Branch name (attaching the screenshot)
Please let me know if there is any other way to check logs/activity to confirm how are these tags getting created.
<screenshot_removed_for_privacy>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sonam_Moga1,
If the tag is not pushed by your builds, then it is possible that it exists in a clone of the repo (either your clone or the clone of one of your teammates) and gets pushed to Bitbucket when running git push --tags.
Please check the tags on your local clone and see if this specific tag is on your clone. If it is, it will get pushed every time you run git push --tags, so you need to remove it from the clone. I suggest asking your teammates who work on this repo to check the same.
If you still cannot figure it out, you can create a ticket with the support team for further investigation since your workspace is on a paid billing plan. There are no logs for admins/users that show when a tag is pushed to Bitbucket, but the support team may be able to figure this out from our internal logs.
You can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. When you are asked to provide the workspace URL, please make sure you enter the URL of the workspace that is on a paid billing plan to proceed with ticket creation.
Just a heads up, I removed the screenshot from your post to protect your privacy.
Please feel free to let me know if you have any questions.
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.