Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect BitBucket CI pipeline re-run better #9309

Closed
bahmutov opened this issue Nov 24, 2020 · 1 comment · Fixed by #9292
Closed

Detect BitBucket CI pipeline re-run better #9309

bahmutov opened this issue Nov 24, 2020 · 1 comment · Fixed by #9292
Labels
CI General issues involving running in a CI provider

Comments

@bahmutov
Copy link
Contributor

When a BitBucket CI pipeline fails, the user can retry just the failed steps. This does NOT create a new pipeline, instead it increments the environment variable BITBUCKET_STEP_RUN_NUMBER see https://community.atlassian.com/t5/Bitbucket-questions/About-the-BITBUCKET-STEP-RUN-NUMBER-Default-Variable/qaq-p/1319257

We need to send this variable to the Dashboard API when recording so we can properly assign the recordings

@cypress-bot
Copy link
Contributor

cypress-bot bot commented Dec 7, 2020

Released in 6.1.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v6.1.0, please open a new issue.

@cypress-bot cypress-bot bot locked as resolved and limited conversation to collaborators Dec 7, 2020
@jennifer-shehane jennifer-shehane added CI General issues involving running in a CI provider and removed CI: bitbucket pipeline labels Oct 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CI General issues involving running in a CI provider
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants