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

[BUG]: Task IISWebAppDeploymentOnMachineGroup@0 stopped removing files after adding TakeAppOfflineFlag #19380

Closed
4 of 7 tasks
labeled opened this issue Dec 14, 2023 · 1 comment
Labels

Comments

@labeled
Copy link

labeled commented Dec 14, 2023

New issue checklist

Task name

IISWebAppDeploymentOnMachineGroup@0

Task version

0.227.0

Issue Description

We started to notice recently that our destination web folders were growing in size. We have had the RemoveAdditionalFilesFlag set true with the TakeAppOfflineFlag also set true.

Here is a screen shot of the deployment with TakeAppOfflineFlag and RemoveAdditionalFilesFlag being true (note 0 files removed even though there are over 800 files in that directory)
image

Once I removed the TakeAppOfflineFlag the deploy removed the extra files succesfully.
image
image

Looking at my own screen shots, it somehow changed the version of the IISWebAppDeploy task...

Environment type (Please select at least one enviroment where you face this issue)

  • Self-Hosted
  • Microsoft Hosted
  • VMSS Pool
  • Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Windows 10

Relevant log output

No error logs

Full task logs with system.debug enabled

 [REPLACE THIS WITH YOUR INFORMATION] 

Repro steps

No response

@v-mohithgc
Copy link
Contributor

Hi @labeled, I was checking the code changes between the task version 227 and 232, the only change I can see is the upgradation of node handler to Node16.

Just wanted to know, in case if you had enabled this flag "TakeAppOfflineFlag" along with "RemoveAdditionalFilesFlag", what is the behaviors you're observing in the latest version of the task (ie 0.232.1)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants