We have a Octopus Deploy project, which deploys package content to a filer.
It works great. But sometimes, when a file on the destination side is used by other users/processes, the deployment would fail because the destination file has a handle on it and is read-only.
Is there a way to automatically skip/exclude that file during the deployment if the file on destination side is read-only?
Thanks for getting in touch!
This is something that we do not allow as part of a deployment in Octopus, as we consider this to be bad practice (what if the file that is locked is required to be updated as part of the deployment). What I would recommend in this case would be to investigate the use of a blue/green deployment pattern, to allow for a safe deployment of your new version.
If you have any questions please let me know,
Thanks for the clarification!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.