I have a simple project with two steps within it. The first step runs a powershell script targeted at a role named ‘environment-host’, which simply executes
Write-Verbose “Hello World”
Against a target machine with that role in an environment, so that the project can register a deployment for a given release for that environment, so that triggers can then work.
The second step is a simple nuget package deployment to an IIS website.
The behaviour I am seeing is that if I do a deployment and target a specific machine (the ‘environment-host’ machine), that deployment executes the first step and skips the second, and I will have a successful deployment of this release of the project registered in that environment.
But immediately after it executes the project trigger attached to the project seems to fire. The trigger is set up as so:
New deployment target becomes available for QA with role web-server
The final piece to this is that I have four ‘dead’ machines with a role of web-server in the environment that have been torn down via cloud formation, but Octopus has not yet cleaned up with their machine policies, which is set to clean them up if they don’t pass a healthcheck within an hour.
Let me know if you need any more info.
ServerTasks-131.log.txt (6 KB)