Set Variables from octo.exe create-release
It would be useful to be able to set the value of octopus variables as part of the octo.exe create-release command.
In our case, we would like to use some values from the build server in our web configuration (branch name). We are currently able to work around this by including the branch name in the package name (we could alternatively write it to a text file in the package), parsing it out using a regex and setting an octopus variable using a powershell script but it it cumbersome and fragile. Additionally, variables set from powershell scripts cannot be used in Nested Variables, so we are required to set every variable that uses the branch name explicitly in the powershell script.
Jason Armitage commented
I would like to use a variable in the package ID, but currently can't pass in variables when creating a release.
So currently I either have to have a project for each possible package ID or have one project with a step for each package, then ignore packages that haven't changed. Not fun for 10s-100s packages. Keeping all the projects in sync.
I have run into the same problem, in using Variables and using the --variable=VALUE switch.
I need to be able to deploy to several environments without duplicating projects.
I am using Octopus 3.06 but it seems to be not working. Has anybody got it working in 3.06 or later I am not sure this is actually working yet.
I keep getting the error below:
The step failed: The package 'Website xxxxxxxxx' is required by 'Deploy Application xxxx', but no NuGet feed has been specified.
How to pass the deployed by username(from jenkins) using octo.exe
Laurentiu Macovei commented
Octo.exe seems to be supporting this but there is no clue of how to use it
-v, --variable=VALUE [Optional] Values for any prompted variables in
the format Label:Value