Plans to implement good way to document a deployment?

(jimlocke2) #1

Is there anything in the works, or, a recommendation on a reliable way to document the Package names, and machines that the packages are deployed to, during a deployment?

I’ve got a bunch of code in an email step, that uses variables set at each package step, however it’s getting hard to manage, and doesn’t work reliably.

Thanks.

(Daniel Fischer) #3

Hi @jimlocke2,

Thanks for getting in touch! Currently we do not have any built in method for achieving what you are after here. We had a chat about the idea of a single variable which could return this kind of value. However, it looks like it would actually be a fairly complex thing to achieve on our end. I think the method you are using of writing custom code in your email step and calling variables from each package step is the best method for achieving this at the moment.

We do have a system variable which will resolve to all machines targeted in a deployment. The drawback of this variable is that it is not specific to package deployments and returns ID, not Name. As an example, a script step against a target you are not deploying a package to would be recorded with this variable.

#{Octopus.Deployment.Machines}

This probably does not help you, though I thought I would mention it anyway.

I’m sorry I could not provide a more helpful answer on this one. If you have any further thoughts or questions here, please let me know.

Best regards,
Daniel

(jimlocke2) #4

Thanks for the reply Daniel.

I’m hoping the issue with Output variables in child steps will be fixed at some point.

Until that time, we have no reliable way to capture and targeted machines and some other info (from output variables), with our project using child variables.

It sounds like this issue was fixed some time ago, but has reappeared at some point.

(system) closed #5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.