Hi,
We have what I would think would be a common requirement, but can’t see from the documentation how to achieve it.
We are deploying 5 steps to a machine, there are 10 machines in the environment. The requirement is that if one step fails then the installation on that machine fails, but the other machines in the environment continue installing. The default functionality we are seeing is that all machines are deployed to in parallel, if one step fails the whole release is aborted and failed.
We seem to have achieved what we require by setting the deployment up to have a guided failure. This allows us ignore the failed step and skip the current machine, but continue with the rest.
However it would be preferable to have this functionality without requiring human interaction, an example of this would be for scheduled deploy to QA environment, we might want to set this running at 03:00 when all users are out of the system. The default behaviour would be on step fail to skip that machine and carry on with all others, but as no one would be around to guide the failure our current solution won’t work.
My questions are :
Can we setup the system to be by default on step failure, fail the machine, but continue to the next screen ?
Can you point me to any documentation that explains the step “run conditions” or documents that show the relationship between step fail and machine / release fails ?
Thanks
Jon