Re : Tagging in SQL format changeset

It is not clear to me why you are running the generateChangelog command repeatedly. Typically this is only done once, when you first start using Liquibase, to generate an initial changelog. 

You should not need to repeatedly use the liquibase clearchecksums command either.

Then on your final bit - if you want to apply a tag to the database, then there are two ways to do it. You can add a <tag> element to your master changelog, OR after you run the liquibase update command, you can run the liquibase tag command. Doing it with the <tag> element in the changelog ensures that the tag is applied in the same way on every database that you run update on. Doing it with the tag command is a more 'ad-hoc' way of doing it, and requires that you run the command on every database you want to have the tag on. 

Steve Donie
Principal Software Engineer
Liquibase Community Engagement
Datical, Inc. http://www.datical.com/