We are using version 2018.7.7 and noticed an odd item when a deployment includes steps that will not actually be run on a server during that deployment because that Role is not assigned to the Machine being deployed to. What we end up seeing is that the time it displays overall that it took to run the step is the overall time at that point in the deployment process, not how long the step itself took. Here’s an example:
You will notice that the “Create Delete Combit Files Task” took 3 seconds to run, but the “Deploy Notification Engine” step, which will be skipped because no machines being targeted for deployment had that role, took 2 minutes and 8 seconds. If you look at the detailed information between the two steps, you will see that only a second has gone by. We would expect to see that the “Deploy Notification Engine” step took 1 second to run.
This isn’t causing our deployments to slow down, but more than likely, just an UI issue that we wanted to pass along.
If you have any questions, please let me know.
Automation & Installation Engineer