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

Cypress Cloud Uses Wrong Branch in Semaphore CI #26309

Closed
leightjohnson93 opened this issue Mar 30, 2023 · 2 comments · Fixed by #26333
Closed

Cypress Cloud Uses Wrong Branch in Semaphore CI #26309

leightjohnson93 opened this issue Mar 30, 2023 · 2 comments · Fixed by #26333
Assignees

Comments

@leightjohnson93
Copy link
Contributor

Current behavior

In Sempahore CI, on pull requests, Cypress Cloud test runs show up under the target branch.

Desired behavior

Test runs should show up as being run on the current branch.

Test code to reproduce

Cypress uses SEMAPHORE_GIT_BRANCH as the branch to report test runs. However, for a pull request this points to target branch. This is a problem, because we want the current branch.

branch: env.SEMAPHORE_GIT_BRANCH,

https://docs.semaphoreci.com/ci-cd-environment/environment-variables/#semaphore_git_branch

Cypress Version

12.8.1

Node version

16.13.0

Operating System

Ubuntu 20.04.6 LTS (Focal Fossa)

Debug Logs

No response

Other

No response

@emilyrohrbough
Copy link
Member

I confirmed we are using the wrong ENV. Per the docs:

In builds triggered by a Pull Request, the value of the SEMAPHORE_GIT_BRANCH is the name of the git branch targeted by the Pull Request.

@cypress-bot
Copy link
Contributor

cypress-bot bot commented Apr 17, 2023

Released in 12.10.0.

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

@cypress-bot cypress-bot bot locked as resolved and limited conversation to collaborators Apr 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants