Custom Release Properties Like Team City Build Id
I'd like to capture some additional fields along side every release.
For example, every release of my project, should have a corresponding:
- Team City Build Number
- Team City Build Type Id
- Team City Build Id
At the time of creating a release in Octopus, if done through the octopus UI - these values would be prompted for.
If done through Octo.exe then the create release command should have the ability to set these release specific property values.
The reason this is useful is because:
- The Octopus Release number no longer has to match the Team City build number in order to tie the 2 up together. You could edit an existing release number, and would not break the link between the release and Team City, because the Team city build id for the release would be held in an additional property of the release.
- Can store additional useful properties relating to the release such as paths to assets such as coverage reports etc.
At a releases level, i'd like to have the ability to define some custom fields (similar to the step template fields) that would be filled in whenever a release of the project is created.
that must be filled out for each release that is created.
I think this would also address this: https://github.com/OctopusDeploy/Issues/issues/1149#issuecomment-52598811
Jasper Nygaard commented
+1. Wanting to set optional (no prompt) variable, specifying JIRA issue(s). Will be used in a step, updating related issues that a release have been deployed to a given environment.
Darrell Tunnell commented
- in case it wasn't obvious - i'm not suggesting octopus adds these as 3 concrete fields - i'm suggesting Octopus provides the ability for a user to define a custom set of properties held against a release, and settable at the time of release creation. I am imagining you would define this list of fields at a project level, and if you defined any, they would appear on all future release creations.