1. A third option for if the destination file exists: don't copy, but don't fail either. Currently, you can set it to fail, then "ignore failure", but then you're suppressing other errors, like if the source file doesn't exist.
2. The default for Copy File should be to "fail if zero files affected". If the file I'm copying can't be found, that's almost certainly an error I want to know about.
3. The default for Delete File should be the opposite: If all I want to do is make sure a file doesn't exist, why do I care whether it was there before or not? The defaults for this and Copy File seem to be backwards.
Thanks for the suggestions. (1) and (2) will be in the next major release, thanks for pointing them out. If you need the skip-existing functionality right now, it's present on the Copy/Move FileSet action.
With (3), I think we'll probably leave the default as-is.
Although you're right that it is no major issue if the file doesn't exist, most of the time for an automated process you want to know that things are working as you expect - so if you want to delete a file, you'd expect it to be there and if it's not then it could be masking another problem, like a mistake in the pathname or a problem with an earlier stage of the build.
Although you’re right that it is no major issue if the file doesn’t exist, most of the time for an automated process you want to know that things are working as you expect - so if you want to delete a file, you’d expect it to be there and if it’s not then it could be masking another problem, like a mistake in the pathname or a problem with an earlier stage of the build.
Yeah, that’s reasonable.
>Keep the suggestions coming.
You’re a glutton for punishment Quick suggestion: keys to focus the build log and current action list. Those two and the “action types” list are the most common areas to want to be, it would be great to be able to zip around all three with the keys.
Hmm. I actually have a build here with a keyboard binding for “View Log” already (better keyboard integration is something we’ve been focusing on.) Will see about the current action list.
Quick suggestion: keys to focus the build log and current action list. Those two and the “action types” list are the most common areas to want to be, it would be great to be able to zip around all three with the keys. 