We are using $BITBUCKET_BUILD_NUMBER to identify our test runs in cypress, however if we retrigger a step then the $BITBUCKET_BUILD_NUMBER value is the same.
Is there any built in variable that will give us the run number as well, or a unique identifier per step run?
Hi @John C ,
Is your use case re-triggering failed steps of a pipeline via the UI?
There is a unique identifier per step, you can use $BITBUCKET_STEP_UUID.
Please note though that when you rerun a failed step, the rerun will have a different $BITBUCKET_STEP_UUID than the original one.
It is therefore not possible to keep track of the run number in this case, since the step UUID changes. But you have a unique identifier for this step via $BITBUCKET_STEP_UUID.
Is this something that works for you?
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events