You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I did not find exactly the answer in your docs, and it mentions to open an issue for a different CI environment.
I have the following setup:
My repository is hosted on github
For reasons, I have a github action, that mirrors the repository to gitlab, because private runners are connected to gitlab
Now the codspeed runs in an gitlab environment
I want the report go to github, not gitlab
So the PR exists on github, while the actual CI is running in a mirror repository that has a gitlab environment.
Now I know that you support both github and gitlab environments, but there are probably some assumptions that are just not true in the setup that I have. For instance there is no MR on the gitlab side, only the branch.
Any chance to trick codspeed to believe that it is a github environment, and which variables would I need to set, such that the report would be sent to the github repository?
Thanks for figuring this out.
The text was updated successfully, but these errors were encountered:
art049
changed the title
Different CI environment
Support GitlabCI on a GitHub repository
Feb 19, 2025
Hello,
I did not find exactly the answer in your docs, and it mentions to open an issue for a different CI environment.
I have the following setup:
So the PR exists on github, while the actual CI is running in a mirror repository that has a gitlab environment.
Now I know that you support both github and gitlab environments, but there are probably some assumptions that are just not true in the setup that I have. For instance there is no MR on the gitlab side, only the branch.
Any chance to trick codspeed to believe that it is a github environment, and which variables would I need to set, such that the report would be sent to the github repository?
Thanks for figuring this out.
The text was updated successfully, but these errors were encountered: