The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Pipeline: Unique step ID when retriggered

John C
March 23, 2021

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?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 29, 2021

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?

Kind regards,
Theodora

John C
March 29, 2021

Thanks Theodora, 

 

That would work, as a work around we generate a random number and append it to the buildID so this is the same and allows us to use a built in ID.

Like Theodora Boudale likes this
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events