I'm getting the following banner at the top of the Builds tab in Xcode Cloud Xcode Cloud is unable to connect to your GitLab Self-Managed repository. Reconnect your source control provider so Xcode Cloud can build your source code.Reconnect Clicking on reconnect says that "GitLab Self-Managed has been successfully connected. Xcode Cloud can now access your source code. ". However, when I refresh the page, the banner comes back. In the Settings, there doesn't appear to be any error under repositories. The builds are running and cloning my repo. It's still concerning though. And for context, I was trying to unlink the gitlab self-managed integration in order to re-link it with a different account, which took days to try and figure out since I keep getting errors in some areas, but not others. I ended up trying these steps, and eventually a build kicked off: Remove the app from my personal gitlab profile Remove the integration to gitlab from Users & Access Add the integration from Users & Access with the new account (creating the app in gitlab) In one of the workflows I had already configured, adding a new primary repository, which is just the same link Make sure every workflow is using that "new" primary repository Delete the old primary repository from the xcode cloud settings for my app The instructions for adding a repository really need to be updated for this type of scenario, as well as more verbose error messages and logging. For example, my build was queued for hours with no error message

I've recently being getting an intermittent issue on my builds. My post-clone script calls yarn install to set up dependencies for the app. Occasionally it will fail at this step fetching packages, on what I'm assuming is the package stored in a private gitlab repository for the company. The repository is accessible over the internet for ssh, and uses ssh keys for authentication. I install the private key at the start of the script, it's stored as an environment variable in the workflow configuration. Here's what the error looks like, note that the cert altnames are different every time: [2/4] Fetching packages... error Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: Host: <private-repo.com>. is not in the cert's altnames: DNS:*.outsystemsenterprise.com, DNS:outsystemsenterprise.com at new NodeError (node:internal/errors:387:5) at Object.checkServerIdentity (node:tls:354:12) at TLSSocket.onConnectSecure (node:_tls_wrap:1549:27) at TLSSocket.emit (node:events:513:28) at TLSSocket._finishInit (node:_tls_wrap:953:8) at TLSWrap.ssl.onhandshakedone (node:_tls_wrap:734:12)