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 ?
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.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot