Make clear that "Local Path" in SCP task needs to be relative

Often in field "Local Path" of Bamboo's SCP task configuration, an absolute path is set, though the path there need to be relative to this plan's working directory.

This is clearly pointed out in KB Using the SCP task in Bamboo.

If set wrong, the SCP task will simply fail, typically with an error like "There were no files to upload" or something close to that being written out in the plan's build log.

A way to likely help avoid that happening is to

1. either simlply display something like "Local Path of the file to copy needs to be relative to your Bamboo plan's working directory" below field "Local Path".
2. Or, alternatively and coming along with a bit more programming effort, the path entered there should be verified so to not be a relative path starting at this plan's working directory.
   • On verification fail, the logged out error should then be something like "No relative Local Path in SCP task. Please fix that."