Closed corbob closed 1 year ago
Ok, We don't actually need to put it into a different parameter. We already stamp build.number
and I've confirmed we can use that in chained builds 😁
:tada: This issue has been resolved in version 0.15.0 :tada:
The release is available on:
Your GitReleaseManager bot :package::rocket:
Is Your Feature Request Related To A Problem? Please describe.
On old TeamCity, CCM builds stamped a parameter named
CCMVersion
. The recipe explicitly does this with a check of the build title. It would be good to stamp a pre-agreed parameter (perhaps justVersion
) with this for all builds.Describe The Solution. Why is it needed?
Test Kitchen can be told to build against a specific version. The builds ideally can chain off of each other and test specific explicit builds.
Additional Context.
Encountered this when working on moving from old TeamCity to new TeamCity
Related Issues
N/A