Some files are not removed from build artifact about blt HOT 6 CLOSED

Used rsync --delete in the past, so ++ to that idea

from blt.

This will be an issue with class renaming. The old class files won't get deleted. :(

from blt.

The original goal was to prevent issues when the local site was not up to date. I recommend having the task fail in that case rather than do this weird work around.

• Create deploy directory
• Pull in the most recent version of the artifact branch
• Wipe the directory outside of .git folder
• Copy in the files as necessary
• Attempt a commit / push

This will ensure that the build artifact is clean and there isn't extra stuff in there from before.

We could create an optional flag for the deploy task that force pushes in case something goes wrong.

from blt.

To be clear, I'm pretty sure this is only a problem for files that exist in the repo root or outside of the "standard" directories (i.e. docroot, config, hooks, etc...). Which begs the question... why are files being created outside of these directories? Seems like an edge case that could be handled with a custom deploy step.

On the other hand, I don't see a problem in just nuking the deploy directory before copying files there, or using rsync --delete. Although we'd want to make sure to leave the git directory intact.

from blt.

#162

from blt.

Seems like we can close this via #162

from blt.