nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

doDeletes and TeamSite Comparison

gschwa

Does the doDeletes transfer rule have any effect when using the TeamSite comparison deployment type?

Find more posts tagged with

Comments

Adam Stoller

Your question is a bit unclear - but the answer is "yes".

If you are doing a TeamSite based comparison (sourceTeamsite) - doDeletes will have an effect.
If you are doing a File System directory based comparison (sourceFilesystem - no filelist) doDeletes will have an effect.
If you are doing a File List based deployment (sourceFilesystem - with filelist) doDeletes will have an effect (if any entry in the filelist does *not* exist on the source side)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

gschwa

Here is a bit more detail...

I am using the sourceTeamsite tag and I am setting the following params:

area = //hostname/default/main/branch/EDITION
previousArea = //hostname/default/main/branch/EDITION/INITIAL

This will push the entire edition to the target server.
The <target> tag in my deployment file looks like this:

<target useReplicationFarm="www1">
<targetFilesystem area="d:/inetpub/wwwroot/website/"/>
<comparisonRules dateDifferent="yes"/>
<transferRules doDeletes="yes"/>
</target>

So i try the following steps:
1) I run the deployment as described above. All the files in the latest edition are succesfully deployed.
2) I create a test text file in the deployment directory.
3) I rerun the deployment in step 1 and test text file is not deleted!!

So why?

Adam Stoller

If you're using sourceTeamsite - then the only comparison performed is between the area and previousArea -- so only those files that differ between those two areas will be deployed / deleted.

If you create another file on the actual target area (d:/inetpub/wwwroot/website/) for your deployment - it is completely outside the scope of the doDeletes in this case.

If instead of using sourceTeamsite you used sourceFilesystem - then any files which exist on the target but not on the source (assuming the absence of filters) will be deleted on the target as part of the deployment.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com