It's not the same without you


Atlassian Community Hero Image Collage

Continuous Deployment with Bamboo (and Grails)


I've been trying to setup a continuous deployment environment by following
So far, I have a grails application with a build plan as follows:
  1. test stage (checkout + grails test-app)
  2. build stage (grails test war + grails prod war) + 2 artifacts defined
  3. deploy stage: tomcat deploy plugin with the war file
  4. manual production stage: again tomcat deploy plugin
The issue is at step 3: I would like to specify the artifact from stage2 as the "WAR file" parameter.
But it only accepts an "hardcoded" war file like "my-application-test-0.01.war", which is not really easy on the long term (after each version upgrade)
Do you have any other solution or workaround ?

1 answer

0 votes

You could use wildcards to define the artifact and then deploy it.

That's step 2, and I got my 2 artifacts defined with wildcards.

The problem is how do I feed the Tomcat deploy plugin with the artifact id/name instead of a "WAR file" (btw I tried wildcards in the "WAR file" input but that doesn't work)

If that does not accept wildcards, the only thing I can think of is symlinking or copying your artifact to a fixed name using a ScriptTask and wildcards before triggerring deployment task.

I found this article too

but it seems there is no other way than "scripting"... too bad defining artifacts is somewhat useless if you can't use it as a parameter for subsequent stages

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Off-topic

Friday Fun: Virtual dance party!

Do dance parties help you relieve stress? How about *virtual dance parties*? My team holds virtual dance parties to brighten the mood of a tough day or celebrate an upcoming weekend.  Want t...

31 views 2 3
Join discussion

Community Events


Find an event


Unfortunately there are no Community Events near you at the moment.

Host an event


Events near you