How to trigger bitbucket pipeline for already available tags in repository.

[Ashish Bilawne]

We have a critical requirement to enable the triggering of Bitbucket pipelines for tags that are already present in the repository. This feature is essential because it allows us to select and deploy from a list of available tags, directly from a dropdown menu.

The primary use case for this requirement is the need to perform rollbacks to previous versions of our code. In the event that we need to revert to an earlier stable version due to unforeseen issues with the current deployment, having the ability to easily select and deploy an old tag is crucial. This capability ensures that we can quickly restore functionality and minimize downtime, maintaining the reliability and stability of our applications.

By implementing this feature, we will enhance our deployment process, making it more flexible and robust, and ensuring that we can efficiently manage both new releases and emergency rollbacks.

[Theodora Boudale]

Hi Ashish and welcome to the community!

Thank you for your feedback.

You could do this in one of the following two ways:

1. Open the Commits page of the repo on Bitbucket Cloud. If the tags are on a branch other than the repo's main branch, select Show all to see all commits.

If you then open the commit with the tag you want to deploy, you will see the option Run pipeline at the bottom of the right sidebar. You can use it to trigger a certain pipeline for this commit.

2. Alternatively, from the Pipelines page of the repo, you can find the older build on the commit/tag that you want to deploy again. If you open the build, you will see an option to Rerun the build (next to the build number).

Do any of these options work for you?

Kind regards,
Theodora