Skip Step If Package with x.x.x.x is Already Deployed To Target Environment
Can we please get a feature added to SKIP steps if the package associated with the step has already been deployed to a target. This seems like a fundamental feature that would be included with the product. If the package associated with a step is less then or equal to the associated package already applied to the target skip step and all child steps, go to next.
Scenario:
- 10 Unique Services Rev'ing as part of the release
- Project Includes Steps for 10 Unique Service Deployments
- 3 applications are changed, and get pushed to the repository
- Project Deployment is executed, all 10 applications have to deploy, even though only 3 are new.
Skip packages that are already installed
Octopus can check whether the same version of an included NuGet package has already been installed on the deployment target and skip further deployment of the package. By default, Octopus will always re-install every included package
Jesse
shared this idea
-
Natalie
commented
We have problems with using the "Skip packages" option as well. We would like to be able to skip all child steps. Here is an example that is not working for us.
Step 1: Deploy Service
Child step 1: Stop service
Child step 2: **Deploy package**
Child step 3: Start service
Child step 4: Remove some unused filesWe would like all 4 of these child steps to be skipped if there is no change to the package in child step 2. Right now, child steps 1, 3, and 4 still run.
-
Chris Camburn
commented
Out of curiosity, in what way does the existing 'Skip any package step that is already installed' not cover your scenario? In use it correctly skips package steps we have.