Grails 2.5.2 automatically running upgrade script before running commands

[Sachin Verma]

When trying to start any Grails task, its getting failed due to following upgrade call which is not available with grails 2.5.2?

Following is the build log:

simple	28-Nov-2015 01:05:36	Starting task 'compile' of type 'com.atlassian.bamboo.plugins.bamboo-grails-plugin:grailsBuilderTaskType'
command	28-Nov-2015 01:05:36	Beginning to execute external process for build '***'\n ... running command line: \n/***/**/bamboo-ebs/opt/grails/2.5.2/bin/grails upgrade -force -non-interactive\

build	28-Nov-2015 01:05:37	| Loading Grails 2.5.2
build	28-Nov-2015 01:05:39	| Configuring classpath
build	28-Nov-2015 01:05:45	| Running pre-compiled script
build	28-Nov-2015 01:05:47	| Error Script not found: Upgrade
simple	28-Nov-2015 01:05:50	Failing task since return code of [

/***/**/bamboo-ebs/opt/grails/2.5.2/bin/grails upgrade -force -non-interactive] was 1 while expected 0
 

How can i remove call to automatic call upgrade script ?

[Przemek Bruski]

I think this happens (and I am not saying this is a correct behaviour) because Bamboo detects a mismatch between the version of Grails you use and the one declared in your app.

Try fixing it by setting app.grails.version in application.properties file. You can do it manually in your code or via a script task started before your Grails task.

[Sachin Verma]

Hi, The version is properly set in application.properties like: app.grails.version=2.5.2 Even manually set down but didn't work. Could you tell how bamboo decides to call upgrade script automatically?

[Przemek Bruski]

OK. It looks like Grails 2.5.2 contains a bug - it introduces itself as 2.5.2.BUILD-SNAPSHOT(https://github.com/grails/grails-core/issues/9349). Try upgrading to 2.5.3, or set the version in grails-2.5.2/build.properties