Uses

The Maven tag goal is typically used to mark the current database state by adding the tag to the last row of the DATABASECHANGELOG table.

Liquibase tag operations

When you run the tag goal and use the tagDatabase Change Type in your changelog file, and they do not match each other, you will have the following:

• If this is the first row in the DATABASECHANGELOG table, a Liquibase internal row is added to the DATABASECHANGELOG table with the tag name specified when you ran the tag goal with the liquibase.tag attribute.

• If this is not the first row in the DATABASECHANGELOG table, the last row in the DATABASECHANGELOG table is updated to include the tag name specified when you ran the tag goal with the liquibase.tag attribute.

• If this is not the first row in the DATABASECHANGELOG table and the last row in the DATABASECHANGELOG table already has a tag, a new tagDatabase row is added to the DATABASECHANGELOG table.

Liquibase update to tag operations

If you want to make an update to a specific tag using the liquibase.toTag attribute, it will work only if there is a tagDatabase Change Type in the changelog:

• When a Liquibase tagDatabase When a changeset is deployed from the changelog, it adds a new row to the DATABASECHANGELOG table, which will have the tag name specified in the changeset.

• When liquibase.toTag is configured, and there is a row in the DATABASECHANGELOG table corresponding to the tagDatabase changeset in the changelog, the update goal deploys all objects up to and including the tagDatabase changeset.

• When liquibase.toTag is configured, and there is no matching tagDatabase changeset specified in the changelog, the update goal deploys all changesets that are not excluded by labels, contexts, dbms, and others.

Liquibase rollback by tag operations

When a Liquibase tag changeset is deployed from the changelog and the liquibase.rollbackTag attribute is configured with a value matching the tag in the changeset, the rollback goal removes all changes that come after the tag changeset. It also rolls back the tag changeset.

When you run liquibase.rollbackTag with the tag specified only by using the tag goal with the liquibase.tag attribute, the rollback command will revert all your changesets after the tag you specify.

Note: It is best practice to tag your changesets before running any other commands against your database.

Maven configuration

You can configure Liquibase Maven in multiple ways. You can pass arguments like <changeLogFile> in Maven directly in your pom.xml file, in a liquibase.properties file referenced in your POM, as environment variables, or as JVM system properties. To learn about each files syntax, see Maven Properties.

Tip: For more information about the Maven configuration, see Configuring Maven.

Additionally, you can include <liquibase.tag>specify your tag here</liquibase.tag> in your pom.xml file under the <properties></properties> in the <project></project> level.

Running the tag Maven goal

Running the tag goal requires a Maven project to be implemented. To run the goal, type the following in your command prompt:

mvn liquibase:tag -Dliquibase.tag=myTag

Maven tag output

When successful, the tag Maven goal produces the following output:

[INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building liquibase-app 1.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- liquibase-maven-plugin:3.9.0:tag (default-cli) @ liquibase-app --- [INFO] ------------------------------------------------------------------------ [INFO] Parsing Liquibase Properties File [INFO] File: liquibase.properties [INFO] 'referencePassword' in properties file is not being used by this task. [INFO] 'changeLogFile' in properties file is not being used by this task. [INFO] 'referenceUrl' in properties file is not being used by this task. [INFO] 'referenceUsername' in properties file is not being used by this task. [INFO] ------------------------------------------------------------------------ [INFO] [INFO] [INFO] Liquibase Community 3.9.0 by Liquibase [INFO] Starting Liquibase at Thu, 09 Jul 2020 09:24:22 CDT (version 3.9.0 #11 built at Thu May 14 04:03:56 UTC 2020) [INFO] Parsing Liquibase Properties File liquibase.properties for changeLog parameters [INFO] Executing on Database: jdbc:oracle:thin:@//win-20e107kb4tn:1521/ORCL [INFO] SELECT COUNT(*) FROM DATABASECHANGELOGLOCK [INFO] SELECT COUNT(*) FROM DATABASECHANGELOGLOCK [INFO] SELECT LOCKED FROM DATABASECHANGELOGLOCK WHERE ID=1 FOR UPDATE [INFO] Successfully acquired change log lock [INFO] SELECT MD5SUM FROM DATABASECHANGELOG WHERE MD5SUM IS NOT NULL AND ROWNUM=1 [INFO] SELECT COUNT(*) FROM DATABASECHANGELOG [INFO] MERGE INTO DATABASECHANGELOG a USING (SELECT * FROM (SELECT ORDEREXECUTED, DATEEXECUTED from DATABASECHANGELOG order by DATEEXECUTED desc, ORDEREXECUTED desc) where rownum=1 ) b ON ( a.DATEEXECUTED = b.DATEEXECUTED and a.ORDEREXECUTED=b.ORDEREXECUTED ) WHEN MATCHED THEN UPDATE SET a.tag='mikev1' [INFO] Successfully released change log lock [INFO] ------------------------------------------------------------------------ [INFO] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6.002 s [INFO] Finished at: 2020-07-09T09:24:25-05:00 [INFO] Final Memory: 20M/450M [INFO] ------------------------------------------------------------------------