How do I prevent Bamboo from reporting Grails errors loading config files that truly do not exist?

Tim Colson November 20, 2011

Grails tries to load a properties config file from four locations (classpath & file locations with .groovy and .properties extension), and reports errors when they do not exist. This isn't an error in the build, so I'm wondering if there is a way to have Bamboo ignore them?

21-Nov-2011 06:21:06 [groovyc] Compiling 1 source file to /users/bamboo/.grails/1.3.7/projects/WIKITOOL-STATS-JOB1/classes
21-Nov-2011 06:21:07 Unable to load specified config location classpath:wiki-stats-config.properties : class path resource [wiki-stats-config.properties] cannot be opened because it does not exist
21-Nov-2011 06:21:07 Unable to load specified config location classpath:wiki-stats-config.groovy : class path resource [wiki-stats-config.groovy] cannot be opened because it does not exist
21-Nov-2011 06:21:07 Unable to load specified config location file:/users/bamboo/.grails/wiki-stats-config.properties : /users/bamboo/.grails/wiki-stats-config.properties (No such file or directory)
21-Nov-2011 06:21:07 Unable to load specified config location file:/users/bamboo/.grails/wiki-stats-config.groovy : /users/bamboo/.grails/wiki-stats-config.groovy (No such file or directory)

1 answer

0 votes
James Dumay
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 27, 2011

Hi Tim,

Bamboo is reporting these as errors because Grails is outputting the warning to stderror. Currently there is no way for Bamboo to suppress these warnings.

Thanks,

James

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events