Follow these steps if you encounter a red exclamation mark under the status column in repository or project settings, indicating an error with Velocity’s connection to that resource
Initial Checks for Repositories (any VCS)
Repository Deletion: Verify if the repository was deleted in your source system. Velocity does not automatically remove repositories deleted elsewhere. If the repository was deleted in your source system, it’s recommended to remove it from Velocity as well.
Credential Changes: Check if the credentials associated with the repository have changed since its last successful sync. If so, please refer to the relevant VCS instructions below.
System-Specific Troubleshooting
GitHub
1. Credential Verification: Velocity uses the credentials of the user who installed the Velocity GitHub app. Ensure these credentials are current and valid. The user might have been removed from the GitHub organization, or their privileges were downgraded. Consult your GitHub Admin.
2. Velocity GitHub App Repo Visibility: Check the GitHub Velocity app's settings to ensure the necessary repository permissions are granted.
3. Connection Establishment:
- Navigate to Settings > Identities.
- Verify if GitHub is connected. If not, select Establish Connection.
- Allow up to 15 minutes for the connection to be established.
GitLab or Bitbucket
Authentication: Both systems allow the use of personal or service accounts via a personal access token. If permissions to the repositories have changed, the token might no longer be valid.
GitLab Specifics:
Ensure the token has
api,read_user,read_repositories,profile,email, andbrowse permissionsenabled.Check permissions at the repository level due to GitLab's granular access controls.
Bitbucket Specifics:
Tokens should have read permissions for
account,workspace membership,projects,repositories,pull requests,issues,snippets, andpipelines.Ensure read/write permissions for webhooks.
If a token expires and syncing attempts trigger Bitbucket's captcha, visit the service account profile to remove the captcha.
Jira Projects
If syncing with a Jira projects fails:
Confirm the user or service account with credentials still exists, and has access to the specific project.
Check if the project was renamed or archived in Jira
Additional Support
If the above steps do not resolve your issue, please contact the Code Climate support team for further assistance.