Git Integration for Jira Self-Managed (Data Center/Server) Documentation

Contact Support

Cannot auto-deploy some tracked repositories — Specified origin is incorrect or not supported

Problem

Git Integration for Jira application is not able to index repositories from a self-hosted GitLab or GitHub server.

Diagnosis

List of repositories may load in the wizard correctly – but repositories are not indexed.
Logs contain a message similar to:

Сan't auto-deploy a new repository http://gitlab-server.company.com/path/repository.git
com.bigbrassband.jira.git.exceptions.InvalidRemoteOperationException: Specified origin http://gitlab-server.company.com/path/repository.git is incorrect or not supported

Cause

GitLab or GitHub permissions of the service user connecting Jira (via the Git Integration for Jira app) are not sufficient to view source code for the repository.

Solutions

Grant sufficient access to the service account user in GitLab or GitHub:

  • See GitLab permissions (Reporter is minimum required)

  • See GitHub permissions (Read for GitHub organizations or Collaborator for personal owned repositories is is minimum required).

Contact Us
If you still have a question – reach out to our Support Desk or email us at gijsupport@bigbrassband.com.

 

More articles about troubleshooting, workarounds and solutions

Why I am getting the error, “git-upload-pack not permitted”?

Avoid OutOfMemory exceptions by configuring or memory allocation with Jira to accommodate large repositories

Cannot auto-deploy some tracked repositories: Specified origin is incorrect or not supported (this page)

Connection Reset when Accessing the Database

"Dangerous use of multiple connections" error on local database

Duplicate entry 0 for key PRIMARY exceptions in log

Error while reindexing – Java heap space / Object too large, rejecting the pack

Gitolite integration: Why the Git integration app not see the master branch?

Health Check: Database Collation

Indexing error – Too many open files

Installation fails when installing manually

Jira index error: IndexNotFoundException: no segments* file found

Malformed input or input contains unmappable characters

Personal access token failing Azure DevOps integration with Not Authorized error

Problems with shared home on Azure Storage

Pull request index error: org.json.JSONException

Repositories missing from Azure DevOps integration

"Service proxy has been destroyed" exceptions in log

SQLException ‘Incorrect string value’ in merge requests

SSH key file format is invalid

TFS – Not authorized exception when Jira works thru proxy

Unexpected exception parsing XML document from URL error in log

Why don’t I see the Create Branch or Pull Request features?

Have feedback about this article? Did we miss something? Let us know!
On this page