Control SkipIfAlreadyInstalled from Octo.exe force

Legacy Uncategorised
1

Hi,

I asked this a few times on Gthub but didn’t get a response.

Now that you’re added the Octopus.Action.Package.SkipIfAlreadyInstalled to control redeploy behaviour, can this be controlled by the command line?

There was talk about being able to override variables via Octo.exe, and talk of wiring the force parameter up to Octopus.Action.Package.SkipIfAlreadyInstalled to keep compatibility with 1.6. Have either of these been done? Unfortunately SkipIfAlreadyInstalled isn’t of use to us unless we can change it based on context. Sometimes we want to force reinstall of packages, othertimes we don’t. None of our deployments are triggered manually in Octopus directly, as its wired into our Continuious Delivery process.

Thanks,
Mike

2

Hi Mike,

Unfortunately the current 2.0 release doesn’t allow this to be specified on a per-deployment basis (from the UI or command line) - you’d need to define it as a variable and then update the release variables whenever you need to change it.

We do have a plan to fix this in the next release though: https://github.com/OctopusDeploy/Issues/issues/545

Paul

3

Hi Mike,

Unfortunately the current 2.0 release doesn’t allow this to be specified on a per-deployment basis (from the UI or command line) - you’d need to define it as a variable and then update the release variables whenever you need to change it.

We do have a plan to fix this in the next release though: https://github.com/OctopusDeploy/Issues/issues/545

Paul