No application link found for Stash repository: Stash

Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.

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.

*Except Fisheye and Crucible

Problem

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:

1 No application link found for Stash repository: Stash

(Auto-migrated image: description temporarily unavailable)

In the atlassian-bamboo.log you will find a message similar to:

1 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:

1 2 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.
(Auto-migrated image: description temporarily unavailable)

Cause

The problem happened because the Application Link was re-created with a different identifier.

Workaround

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:

  1. Shutdown Bamboo

  2. Backup database for rollback purposes

  3. Look for the latest Bitbucket Server Application Link key with the following SQL query:

    1 select * from BANDANA where BANDANA_KEY like 'applinks%';

    for example: the Application Link key is 8682863e-e2b0-301b-9f0d-32cd6551c329 for the result applinks.admin.8682863e-e2b0-301b-9f0d-32cd6551c329.type

  4. Make sure that the Application Key from Step 3 is the newly created AppLink by checking the URL

  5. Get the list of Repository settings that are not using the above key:

    1 select * from VCS_LOCATION where XML_DEFINITION_DATA like '%stash%' and not XML_DEFINITION_DATA like '%8682863e-e2b0-301b-9f0d-32cd6551c329%';
  6. From Step 5, check what is the existing key used and replace it with the latest key:

    1 update VCS_LOCATION set XML_DEFINITION_DATA=replace(XML_DEFINITION_DATA,'old-key-from-step-5','latest-key-from-step-3');
  7. Restart Bamboo

Resolution

This is fixed as of 5.14.0 - although note that it won't fix repositories that already had the issue:

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.