I'm thinking if the 'Files to deploy' expression does not match any files relative to the $WORKSPACE, the option, if selected, should trigger a build failure. For example, the following expression could trigger a build failure if no .jar files were present under the 'output' directory:
This new option, 'Fail build if there are no files to deploy' could be added within the 'Advanced...' button options for the 'Files to deploy' field. The problem we're having is that if there are zero files to deploy, the ArtifactDeployer plugin currently indicates that zero artifacts being deployed is a success condition. I'd be useful to have an option to say that, if no artifacts were found to deploy, some error prevented the artifacts from being available for deployment when they were expected per the build configuration.
Thanks for your quick response!