.net - msdeploy/Web Deployment Tool deploying too many files -
We are using our sites to deploy our servers in different environments from our continuous integration server.
Artworks have been manually deployed from command line to dev site. Deployment only pushs changed files and is very fast.
However, when we put pressure on our test or live environment, there is a lot of copying of files from the deployment, which should not be changed. I understand that msdeploy is based on timestamp, size and attributes. Comparisons, which should not be changed.
We can see the use of the switch -whatif that many files are being reported because they do not really change. Especially umbraco core files (this is a umbraco web site).
Anyone walked before this?
Our only idea is to exclude the possible artifacts from Build but we want to correct it properly.
This is a problem where server time was slightly different for our network time.
Adding the following on the command line has corrected it.
-usable rules: SkipNewerFilesRule
Comments
Post a Comment