Specifying package versions by packageId for a release

Legacy Execution
1

From https://octopus.com/docs/api-and-integration/octo.exe-command-line/creating-releases :

Specifying the package version
For each step that has a package, the version is determined in the following order:
    The step name matches a --packageVersion parameter or a file filename found by --packagesFolder
    The package id matches a --packageVersion parameter or a file found by --packagesFolder
    The value from the --package parameter"

Is this correct? It seems that 1) the packageversion parameter does not accept either a step name or package id, and 2) the package parameter does not accept a packageid, only a step name.

I’m trying to script the release creation using only a set of explicit packageids and versions. I’d really rather not bake knowledge of the step names into upstream processes. Is there a way to accomplish this?

2

Looking at the code, I believe this is a bug in the octo.exe tool. I have a fix and will submit a PR.

3

Hi,

Thank you for the PR! I’ll get a new build out as soon as the CLA is signed and it is merged.

Regards,

Robert W

4

Should be ready to go now.

I think the documentation is still inconsistent. I think the --packageVersion and --package argument names are swapped?

i.e. It should say:

For each step that has a package, the version is determined in the following order:
    The step name matches a --package parameter or a file filename found by --packagesFolder
    The package id matches a --package parameter or a file found by --packagesFolder
    The value from the --packageVersion parameter
5

Hi,

Yes you are right. I’ve fixed it up. An updated Octo.exe should be hitting the download site soon (4.15.5). The TeamCity plugin will follow later today.

Robert W