Quantcast
Channel: Liquibase Forums
Viewing all articles
Browse latest Browse all 2993

Re : "runalways" changesets seem to break rollback functionality

$
0
0
Hi Sam,

good point, didn't think about that.
Just a wild guess, you may add a rollback to your tagging ChangeSet, that does the cleanUp in the Liquibase History Table for you.

  1. <rollback>
  2. <sql>
  3. delete from liquibasechangelog where ID > 'tag-${build.number}' and AUTHOR= 'me' and FILENAME ='<your-changelog-file-here>'
  4. </sql>
  5. </rollback>
I see this is pretty raw especially as it may cause problems when the buildnumbers do not fit into string comparison (jumping from 999 to 1000, comparing real numbers is certainly better but i guess you get the idea). and you'll still have to pass the targeted build number around... but I don't see how this can be fixed.

kind regards
Daniel

Viewing all articles
Browse latest Browse all 2993

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>