We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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
BITBUCKET_STEP_RUN_NUMBER
We need to send this variable to the Dashboard API when recording so we can properly assign the recordings
The text was updated successfully, but these errors were encountered:
Released in 6.1.0.
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.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
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/1319257We need to send this variable to the Dashboard API when recording so we can properly assign the recordings
The text was updated successfully, but these errors were encountered: