Bug 541394 - Push to Atlassian Bitbucket Smart Mirror fails
Summary: Push to Atlassian Bitbucket Smart Mirror fails
Status: NEW
Alias: None
Product: EGit
Classification: Technology
Component: Core (show other bugs)
Version: 5.1   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-21 05:02 EST by Jörg Dissauer CLA
Modified: 2018-11-21 05:58 EST (History)
2 users (show)

See Also:

Attachments
Screenshot of push error (24.35 KB, image/png)
2018-11-21 05:02 EST, Jörg Dissauer CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jörg Dissauer CLA 2018-11-21 05:02:49 EST 
Created attachment 276640 [details]
Screenshot of push error

When connected to a mirror repository of BitBucket Data Center as the origin repo, pushing commits should redirect the push to the primary instance of the data center.

Works well with standard git version >=2.15.0 from CLI.

With JGit/EGit the push fails with the error message shown in the attached screenshot.
Comment 1 Thomas Wolf CLA 2018-11-21 05:58:47 EST 
Please provide more info. We would need to know what you git config looks like, and we would need to have a log of the HTTP interactions, including server responses. Need to know if the server sends back redirects, and if so, what's the original URL and what is the new one. Also, does this happen on the GET or on the POST? Do you have any http.* configuration in the git config (including your user config)? Any "insteadOf" or "pushinsteadOf" configs? What are the remote configs? Any proxies involved?

Does it work if you simply set the push URL to the correct original primary instance?