-
Type:
Suggestion
-
Resolution: Unresolved
-
None
-
Component/s: DVCS Accounts
-
1
-
4
Jira automatically creates post-commit webhooks in GitHub.com when linking a repository via the DVCS connector. These use a url similar to:
http://jira.example.com/rest/bitbucket/1.0/repository/5/sync
Our Jira runs behind our firewall, so the default Jira URL is inaccessible from GitHub.com. We can set up a reverse proxy at another URL (restricted to GitHub's IP addresses) that proxies sync requests to our internal Jira. However, linking new repositories is a manual process:
1. Link repository in Jira
2. Manually change the two auto-created GitHub webhooks to use our reverse proxy.
It would be great if DVCS had a "reverse proxy endpoint" option that would allow customizing the base url for the post-commit hook. That way, instead of adding hooks for
http://jira.example.com/rest/bitbucket/1.0/repository/5/sync
it would add hooks for
http://gh-jira-proxy.example.com/githubsync/rest/bitbucket/1.0./repository/5/sync
For comparison, the GitHub Jenkins plugin does something similar: https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Plugin#GitHubPlugin-Jenkinsinsideafirewall
- was cloned as
-
JSWSERVER-20282 Allow specifying proxy url for auto-linked Bitbucket Cloud post-commit hooks
- Gathering Interest
- links to