No application link found for Stash repository: Stash
Platform Notice: Server, Data Center, and Cloud By Request - This article was written for the Atlassian server and data center platforms but may also be useful for Atlassian Cloud customers. If completing instructions in this article would help you, please contact Atlassian Support and mention it.
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 は除く
問題
After recreating the AppLinks on Bamboo, some Bamboo Plan Branches "Build summary" screens will:
- Stop notifying Bitbucket with the Build Status
- Stop being triggered by Commits done to its Bitbucket branches
A message will be displayed:
No application link found for Stash repository: Stash
In the atlassian-bamboo.log you will find a message similar to:
2016-11-05 03:14:16,123 INFO [AtlassianEvent::0-BAM::EVENTS:pool-3-thread-14] [DefaultErrorHandler] Recording an error: No application link found for Stash repository: Stash : YOURPROJECT-YOURPROJECTPLN4950
On another note, you will find that the Plan Branches now don't recognise the newly created AppLinks. The following message and screens are displayed:
Stash application link required
Your application link to this Stash server has been removed. You will need to link it again to use the available repositories and branches.
原因
The problem happened because the Application Link was re-created with a different identifier.
回避策
To fix that issue, you will need to fix the "Plan Branches" directly on the database.
Please perform the following steps to update it from the database:
- Shutdown Bamboo
- Backup database for rollback purposes
Look for the latest Bitbucket Server Application Link key with the following SQL query:
select * from BANDANA where BANDANA_KEY like 'applinks%';for example: the Application Link key is
8682863e-e2b0-301b-9f0d-32cd6551c329for the resultapplinks.admin.8682863e-e2b0-301b-9f0d-32cd6551c329.type- Make sure that the Application Key from Step 3 is the newly created AppLink by checking the URL
Get the list of Repository settings that are not using the above key:
select * from VCS_LOCATION where XML_DEFINITION_DATA like '%stash%' and not XML_DEFINITION_DATA like '%8682863e-e2b0-301b-9f0d-32cd6551c329%';From Step 5, check what is the existing key used and replace it with the latest key:
update VCS_LOCATION set XML_DEFINITION_DATA=replace(XML_DEFINITION_DATA,'old-key-from-step-5','latest-key-from-step-3');- Restart Bamboo
ソリューション
This is fixed as of 5.14.0 - although note that it won't fix repositories that already had the issue:
- BAM-12330 - Getting issue details... STATUS