Unable to synchronize bitbucket repositories with Jira Server instance
プラットフォームについて: Cloud、Server、および Data Center - この記事はすべてのプラットフォームに等しく適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
要約
Upon integrating Jira Server with Bitbucket Cloud, repositories list doesn't appear in Jira server under DVCS accounts → Bitbucket workspace(workspace ID)
診断
In the Jira server logs, typically located at /var/atlassian/application-data/jira/log/atlassain-jira.log, you would see an error message as below,
Caesium-1-3 DEBUG ServiceRunner [c.a.j.p.dvcs.service.RepositorySyncServiceImpl] Repository sync already in progress, ignoring request
This means there was a stale/corrupt repository sync process in progress preventing any new repository sync request.
ソリューション
The issue could be to due to the last repository sync process not being terminated gracefully.
- Delete the Link between Jira and Bitbucket Workspace from Jira instance.
- Navigate to "Application -> DVCS accounts", then "Delete" the Bitbucket Workspace with the issue.
- Once the Bitbucket Workspace is removed in Jira, relink your workspace with your OAuth key and secret
- Do ensure that that your OAuth credential do have the right permission described in our document
- If the re-linking doesn't help, restart Jira service, this should remove/stop any stale ongoing sync process that was running previously.
- If required, re-connect Jira Server with Bitbucket Cloud after restart.
- If the issue still exists after following the above steps, please reach out to support team by attaching the support zip logs.
- Steps to generate Support zip:
- If the repositories still do not sync, do provide us with the following detail, as this will help us identify other workarounds:
- Screenshot of your current "DVCS accounts" page
- Support Zip: "System > Troubleshooting and support tools > Create Support Zip"
- If the repositories still do not sync, do provide us with the following detail, as this will help us identify other workarounds:
- Steps to generate Support zip: