Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Octopus files should be removed from deployment #2424

Closed
MJRichardson opened this issue Mar 11, 2016 · 2 comments
Closed

Octopus files should be removed from deployment #2424

MJRichardson opened this issue Mar 11, 2016 · 2 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@MJRichardson
Copy link

MJRichardson commented Mar 11, 2016

As reported in http://help.octopusdeploy.com/discussions/problems/44859

Octopus specific files such as variables.json, variables.secret, bootstrap.ps1 should not be deployed. The ticket above relates specifically to Azure Web App deployments, but they probably shouldn't be left in the application folder for regular package deployments either (e.g. ASP.NET deployments).

@MJRichardson MJRichardson added the kind/bug This issue represents a verified problem we are committed to solving label Mar 11, 2016
@MJRichardson MJRichardson changed the title Azure Web App deployment should not include Octopus files Octopus files should be removed from deployment Mar 11, 2016
@MJRichardson MJRichardson added closed/duplicate This issue was closed as a duplicate of another issue ready and removed closed/duplicate This issue was closed as a duplicate of another issue ready labels May 8, 2016
@MJRichardson MJRichardson self-assigned this May 8, 2016
@MJRichardson MJRichardson added this to the 3.3.13 milestone May 9, 2016
@MJRichardson
Copy link
Author

Release note:Prevent Octopus working files (e.g. variables.json, bootstrap.ps1, etc) from syncing during Azure deployments.

@tothegills tothegills modified the milestones: 3.3.14, 3.3.13 May 20, 2016
@lock
Copy link

lock bot commented Nov 26, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

2 participants