Yes. PLEASE! I'd buy multiple for colleagues.
I'm not following you on what you mean by 'build'. Do you mean a project? Or are you speaking of the different versions/builds of Octopus Deploy itself?
Have you looked at the elastic and transient environments capability?
Specifically the 'Deploy to transient targets'?
It might be what you're looking for. You can create the targets, assign roles and all and they would initially be 'unavailable', in your process you might have a step that would create those targets, add a step to perform a health check (mentioned in second link) the process would see the new targets available and the remaining steps would be able to use those newly available targets.
Have you tried 'Channels'? Within the project you could clone a step, then set it's channel to 'branch-2.0' and set the original to 'main' or similar. When you create a release you can select the 'branch-2.0' or 'main' depending on what you are targeting for release. Once you've got the new step doing what you want, set it to the 'main' channel and then delete the original. You can apply Channel filters to the variables as well.
I believe this is already available, when creating a step template select the 'Deploy a Package' type. Much like 'Deploy a package' in a project's process. You can then customize the pre,deploy,post powershell scripts in that template.
You can't do exactly what you are stating (add a package variable) to a 'run as script' template, start from the 'Deploy a package' one and that may help.
Bump on this one. This has bit us in the past..wait coworker just updated me. Still biting. Just to clarify I'm referring to server roles (in environment dashboard). I simple name new and then remove the old is what causes the extra workload.
We’re going to start on this very soon. I’d love to collect more examples of what people want to do with plugins (not so much how the plugin would work/what kind of extensibility, but the actual problem you want to solve)
Custom steps: In our case we'd like to be able to have a step that would check the ticket manager (MS Service Manager here) to verify that either a ticket exists for this promotion or just create a ticket based on the Octopus Variables to reduce processing lag.
It can be done with powershell but sometimes it's nicer to be in the C# development side and potentially share the plugins as a NuGet if possible.