OctopusDeploy/Octopus-Tools — pull request #11 by lisac (2012-04-30 13:36:47+00:00)
Title: define package-specific versions when creating release

Octo.exe create-release has option "packageversion", which assembles a release in which all packages share that version number.

To handle situations where a release candidate might deploy multiple packages, I added option "packageversionoverride", which can be defined multiple times and populates a dictionary (key: packageID; value: versionNumber).

Sample use:
for project "MyProject" whose deployment steps include installing packages "LibraryA", "LibraryB" :
Octo.exe create-release --project="MyProject" --packageversionoverride="LibraryA:1.0.3" --packageversionoverride="LibraryB:2.0.1" ...

When Octo.exe assembles the release, for each step it first consults the packageversionoverride dictionary for a version number (my change); then the packageversion option for a version number; and then resorts to the most recent package.

Would you please consider incorporating these changes in the master?

Thanks for your time.