GitLab connection issues
Incident
Report for Bitrise CI
Resolved
The root cause is now fixed. Important: affected users should reconnect their GitLab accounts on the Bitrise profile page for a permanent fix one more time.
Monitoring
A fix has been implemented and we are monitoring the results.
Update
Customers using GitLab as a git provider can experience problems on Bitrise:
- Bitrise build statuses are not reported to GitLab pull requests
- If the `bitrise.yml` file is stored in the git repo, Bitrise can't access the workflows and start builds
- When adding a new app to Bitrise, it won't be able to find repos of a connected GitLab account
While we are working on the fix, there are some workarounds for affected customers.
For an immediate workaround, recreate the connection between Bitrise and GitLab by disabling and re-enabling the GitLab connection on the Bitrise profile page. This is a temporary workaround and the access needs to be renewed every 2 hours.
There is another workaround for reporting the build status to GitLab: adding the GitLab status Step (https://www.bitrise.io/integrations/steps/gitlab-status) to the workflow, which needs a GitLab personal access token. This token needs a manual expiration date and can be set to a further date.
For users who store their bitrise.yml in their GitLab repo, the workaround is moving the file contents over to the Bitrise workflow editor.
- Bitrise build statuses are not reported to GitLab pull requests
- If the `bitrise.yml` file is stored in the git repo, Bitrise can't access the workflows and start builds
- When adding a new app to Bitrise, it won't be able to find repos of a connected GitLab account
While we are working on the fix, there are some workarounds for affected customers.
For an immediate workaround, recreate the connection between Bitrise and GitLab by disabling and re-enabling the GitLab connection on the Bitrise profile page. This is a temporary workaround and the access needs to be renewed every 2 hours.
There is another workaround for reporting the build status to GitLab: adding the GitLab status Step (https://www.bitrise.io/integrations/steps/gitlab-status) to the workflow, which needs a GitLab personal access token. This token needs a manual expiration date and can be set to a further date.
For users who store their bitrise.yml in their GitLab repo, the workaround is moving the file contents over to the Bitrise workflow editor.
Identified
The issue has been identified and a fix is being implemented.
Investigating
We are currently investigating this issue.
This incident affected: GitHub Webhooks.