How can I make bamboo use a specific version of a liquibase changeset?

[Jeff MacDonald]

I had a realy hard time coming up with a succint topic for this one.

Imagine:

- we do a build on monday

- on tuesday Greg submits an sql change and updates liquibase manifest. we are fully aware that these changes break mondays build but they’re important for next weeks work

- on wednesday we decide to push mondays build to production. ( using deployment projects)

On wednesday if we do a fresh checkout of the source so we can run liquibase we’ll accidently run a patch that we didn’t want to, which breaks the app.

Here are the 2 routes I’m going in an attempt to address this:

a: when we make the release build, export the liquibase XML file as an artifact. Then convince liquibase to use that file from that build.

b: when we do the deployment plan, have it checkout the GIT source from the tagged version that the releaes was build from.

I’m all ears.

[Orlando_Kelly]

Hi Jeff, I'm also investigating Liquibase with Bamboo, did you ever come to a resolution for the issue you mentioned?