Problem Definition

Whenever new changes are pushed, Bamboo scans the repository and typically update specs plan. In that plan, the build starts with checking out a repository in which it's defined. However, when we run a customised build and the repository is checked out at a specific revision, Bamboo does not update specs plan with the current contents of that respective revision, instead the last "saved state" is parsed and executed. That means, for any custom revision, the specs from the last "Specs configuration update" build is used.

Steps to reproduce:

1. Push new changes followed by another to YAML specs repository. This creates 2 new builds with 2 "Specs configuration updated"
2. Now, hit "Run -> Run customised..." and give Revision number of the first revision.
3. The custom build will be executed, however, the Specs configuration update will still use the latest one. 

Suggested Solution

When a customized build is run with a custom revision (using Run customised... option), Bamboo should use the specs from exactly that revision, as the YAML specs definition content might differ.

In other words, when we run a customized build and the repository is checked out at a specific revision, the expected behavior should be that if there is a specs file, it's current contents (from that revision) should be parsed and executed, and not the last "saved state".

Workaround (Optional) 

There is no workaround for now.