Promote Action uses wrong dependency

We're using TeamCity v 9.0.1 and we've encountered a serious issue.  A custom run dialog only shows the last 20 artifact dependent builds as options for a run.  It appears that we should be able to specify and older build by accessing it directly and using the promote button.  However, when selecting a build older than the most recent 20 it defaults to the latest build (or latest pinned, depending on the build configuration).  We execute over 30 builds per day, and we really need to be able to promote older build to different testing environments.  Is there a way to force the promote action to use a specific build?

2 comments
Comment actions Permalink

Hi Samuel,

You can increase the number of builds displayed in dependency drop down using "teamcity.runCustomBuild.buildsLimit=100" internal property.

Could you please explain this phrase "However, when selecting a build older than the most recent 20 it defaults to the latest build (or latest pinned, depending on the build configuration)"? Where do you select this build? Please provide an example.

0
Comment actions Permalink

So build configuration A has an artifact dependency on build B.  I can access the entire history of build B by going to that build configuration and selecting see entire history.  That page has an actions button with a promote option.  Selecting promote on any of the first 20 runs works as expected, but an older run will use latest; not the build run your looking at when you select promote.

0

Please sign in to leave a comment.