Summary

When we try to promote an existing release, after selecting the branch, the screen first loads the latest deployed release (it does not matter if it's from a different branch), after a few seconds the page reloads and the content of the drop-down changes to the latest release from the selected branch.

Steps to Reproduce

1. Create a plan with two branches (ex. master, branch)
2. Create one Deployment project
3. Run a huge number of builds (ex. 5k+ for master and 500+ for branch)
4. Deploy all releases to the same environment.

Expected Results

When you select the branch in the "Promote existing release to this environment" screen, Bamboo should load only the releases related to that branch to avoid an incorrect release to be deployed.

Actual Results

Bamboo loads the latest deployed release and after a few seconds, the page refreshes and the content of the drop-down changes to the latest release deployed from the select branch.

Notes

This situation can cause incorrect releases to be deployed if the user clicks at the "Start deployment" before the page is fully loaded. The following video shows this situation being reproduced.
BSP33361.mp4

Notes from the original reporter (BSP-33361):

Just to further re-iterate our perspective, there seems to be a couple options:

• Tune the performance to load 5k+ release artifacts in < 1 second
• Tune the page to load the last 100'ish artifacts on page load, and only more artifacts if the user does a search or attempts to scroll down the list past the designated loading mark
• Tune the page to not update to the latest /master release once it's done loading all release artifacts ... it seems to override our selection when it shouldn't need to select. It seems there's some logic that says "load artifacts, default to latest"
• Force the page to not allow you to select a branch/artifact until the page fully loads ... maybe gray the selections out and put in a spinning wheel or such.

Workaround

As this problem just happens when you have a huge amount of releases, if you create a more aggressive expiry configuration, the screen will load faster and the bug will not be perceptible.

More information about global expiry you can find at the following documentation:

• Configuring global expiry