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

Enabling and defining custom installation directory feature displays purge when its disabled #4254

Closed
KennethBates opened this issue Feb 7, 2018 · 3 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@KennethBates
Copy link

Octopus 2018.1.4

Steps to repro

  1. Create a package step and enable custom installation directory
  2. Define the directory for CID and leave the purge option disabled
  3. Save the step

When re-entering the step, it displays the following.

01_purge_incorrect

When the CID section is expanded, it correctly shows the purge option as disabled:

02_purge_unselected

When you deploy, the directory is not purged, so it's only a display issue.

Workaround: Enable purging, save the step, disable purging and re-save.

Source: https://secure.helpscout.net/conversation/515556239/23440?folderId=954335 (private link)

@KennethBates KennethBates added kind/bug This issue represents a verified problem we are committed to solving area/modelling labels Feb 7, 2018
@pawelpabich
Copy link

Release Note: Custom Install Directory feature shows now correctly whether files will be purged or not

@lock
Copy link

lock bot commented Nov 23, 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 23, 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

3 participants