The generate-changeset-created-values global parameter is a Boolean that determines whether Liquibase adds timestamps to changesets in the changelog it generates when you run the diff-changelog command and generate-changelog command. By default, it is set to false.


If you use the diff-changelog or generate-changelog commands to create a changelog with the contents of your database, you can set generate-changeset-created-values to true to include a timestamp in the header of each changeset in your changelog. The timestamp is stored as the value of the created parameter and uses the format YYYY-MM-DD hh:mm-ssss.

Setting the generate-changeset-created-values parameter

You can set generate-changeset-created-values in four ways:

  • In the Liquibase properties file
  • As a global parameter in the CLI
  • As a JVM system property
  • As an environment variable (Liquibase Pro)

Liquibase properties file parameter

In Liquibase 4.1+, add the following to Liquibase properties file:

liquibase.generateChangesetCreatedValues: <true|false>

CLI global parameter

Tip: All commands and parameters use the --kebab-case format in the CLI environment. This is the format Liquibase recommends for best results. If your preference is camelCase, it will still work in the CLI.

In your command line, use a global parameter with a single Liquibase command:

liquibase --generate-changeset-created-values=<true|false> generate-changelog --changelog-file=dbchangelog.xml

Java system property

In your command line, use the JAVA_OPTS Environment Variable to set a JVM system property:

Mac/Linux syntax:


Windows syntax:

set JAVA_OPTS=-Dliquibase.generateChangesetCreatedValues=<true|false>

Note: To use a Liquibase command alongside JAVA_OPTS, add && liquibase <command> to the end of your input.

Environment variable (Liquibase Pro)

In Liquibase Pro, set an environment variable:

Mac/Linux syntax:


Windows syntax:


Note: These environment variable commands only apply to the current shell. If you need to pass an environment variable to a child process without affecting the parent process, you can use the export command on Mac/Linux or the setx command on Windows.


If you run a command like generate-changelog with generate-changeset-created-values set to true, the output is:

BEST PRACTICE: The changelog generated by diff-changelog/generate-changelog should be inspected for correctness and completeness before being deployed.
Generated changelog written to C:\<filepath>\dbchangelog.xml
Liquibase command 'generate-changelog' was executed successfully.

The generated changelog includes a created parameter that has a timestamp:

<?xml version="1.1" encoding="UTF-8" standalone="no"?>
	<changeSet author="adrian (generated)" created="2021-08-02 16:26-0400" id="1627936002055-1">
		<createTable tableName="TEST_TABLE">
			<column name="TEST_ID" type="INT">
				<constraints nullable="false" primaryKey="true" primaryKeyName="PK_TEST_TABLE"/>
			<column name="TEST_COLUMN" type="VARCHAR(2147483647)"/>

Related links