`update-testing-rollback`

update-testing-rollback tests rollback support by deploying all pending changesets to the database, executes a rollback sequentially for the equal number of changesets that were deployed, and then runs the update again deploying all changesets to the database.

Uses

update-testing-rollback is typically used when you want to test rollback functionality when deploying changesets in your changelog sequentially. Run this command only when all pending changelogs have been verified as ready to be deployed as you cannot specify changesets to exclude.

update-testing-rollback utilizes a multi-step operation and runs in sequential order:

update changeset1; update changeset2; update changeset3
rollback changeset3; rollback changeset2; rollback changeset1
update changeset1; update changeset2 update changeset3

Note: If you use the earlier versions of Liquibase, the order of operations may differ.

If any of the changesets fail rollback:

Any changesets that come before the failed changesets are deployed to the database.
Any changesets that come after the failed changesets are not tested or updated.

In Liquibase Pro 4.28.0 and later, you can enable Operation Reports to summarize the update-testing-rollback command. This generates an Update Report, Rollback Report, and final Update Report. By default, they are sorted by name:

Update-report-1of3-03-Apr-2024-130655
Rollback-report-2of3-03-Apr-2024-130656
Update-report-3of3-03-Apr-2024-130657

Syntax

To run the update-testing-rollback command, specify the driver, classpath, and URL in the Liquibase properties file. For more information, see Create and Configure a liquibase.properties File. You can also specify properties from the command line.

Then run the update-testing-rollback command:

liquibase update-testing-rollback --changelog-file=example-changelog.xml

Command parameters

Attribute	Definition	Requirement
`--changelog-file=<string>`	The root changelog	Required
`--url=<string>`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`--change-exec-listener-class=<string>`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`--change-exec-listener-properties-file=<string>`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`--context-filter=<string>`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`--default-catalog-name=<string>`	Name of the default catalog to use for the database connection	Optional
`--default-schema-name=<string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`--driver=<string>`	The JDBC driver class	Optional
`--driver-properties-file=<string>`	The JDBC driver properties file	Optional
`--force-on-partial-changes=<true\|false>`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`--label-filter=<string>`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`--password=<string>`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`--report-enabled=<true\|false>`	Enables a report at the command level. Overrides the global parameter `--reports-enabled`. Default: `true`.	Optional
`--report-name=<string>`	Specifies the name of the report file at the command level. Overrides the global parameter `--reports-name`. By default, Liquibase generates a new report file labeled with a timestamp (user's local time). If you set a custom name, Liquibase overwrites the existing file every time you generate a new report. Default: `report-<DD-Mon-YYYY-HHmmss>.html`.	Optional
`--report-path=<string>`	Specifies the file path to the report file at the command level. Overrides the global parameter `--reports-path`. Default: `./`.	Optional
`--report-suppress-exception=<true\|false>`	Liquibase 4.31.0+. Specifies whether to hide exceptions (which may contain SQL) from the operation report at the command level. Overrides the global parameter `--reports-suppress-exception`. Default: `false`. However: If `--report-suppress-exception` is not set and `--report-suppress-sql=true`, Liquibase suppresses all SQL, including exception SQL. If `--report-suppress-exception=false` and `--report-suppress-sql=true`, Liquibase suppresses most SQL but shows exception SQL.	Optional
`--report-suppress-sql=<true\|false>`	Liquibase 4.31.0+. Specifies whether to hide changeset SQL in operation reports at the command level. Overridden by the global parameter `--reports-suppress-sql`. Default: `false`.	Optional
`--rollback-on-error=<true\|false>`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`--tag=<string>`	The tag identifying which tagged changesets in the changelog to evaluate. Specify as `--tag=myTag`. Positional format `<command> <tag>` deprecated in 4.4+.	Optional
`--username=<string>`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

Attribute	Definition	Requirement
`cmdArgs: { changelog-file: "<string>" }`	The root changelog	Required
`cmdArgs: { url: "<string>" }`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`cmdArgs: { change-exec-listener-class: "<string>" }`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`cmdArgs: { change-exec-listener-properties-file: "<string>" }`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`cmdArgs: { context-filter: "<string>" }`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`cmdArgs: { default-catalog-name: "<string>" }`	Name of the default catalog to use for the database connection	Optional
`cmdArgs: { default-schema-name: "<string>" }`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`cmdArgs: { driver: "<string>" }`	The JDBC driver class	Optional
`cmdArgs: { driver-properties-file: "<string>" }`	The JDBC driver properties file	Optional
`cmdArgs: { force-on-partial-changes: "<true\|false>" }`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`cmdArgs: { label-filter: "<string>" }`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`cmdArgs: { password: "<string>" }`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`cmdArgs: { report-enabled: "<true\|false>" }`	Enables a report at the command level. Overrides the global parameter `--reports-enabled`. Default: `true`.	Optional
`cmdArgs: { report-name: "<string>" }`	Specifies the name of the report file at the command level. Overrides the global parameter `--reports-name`. By default, Liquibase generates a new report file labeled with a timestamp (user's local time). If you set a custom name, Liquibase overwrites the existing file every time you generate a new report. Default: `report-<DD-Mon-YYYY-HHmmss>.html`.	Optional
`cmdArgs: { report-path: "<string>" }`	Specifies the file path to the report file at the command level. Overrides the global parameter `--reports-path`. Default: `./`.	Optional
`cmdArgs: { report-suppress-exception: "<true\|false>" }`	Liquibase 4.31.0+. Specifies whether to hide exceptions (which may contain SQL) from the operation report at the command level. Overrides the global parameter `--reports-suppress-exception`. Default: `false`. However: If `--report-suppress-exception` is not set and `--report-suppress-sql=true`, Liquibase suppresses all SQL, including exception SQL. If `--report-suppress-exception=false` and `--report-suppress-sql=true`, Liquibase suppresses most SQL but shows exception SQL.	Optional
`cmdArgs: { report-suppress-sql: "<true\|false>" }`	Liquibase 4.31.0+. Specifies whether to hide changeset SQL in operation reports at the command level. Overridden by the global parameter `--reports-suppress-sql`. Default: `false`.	Optional
`cmdArgs: { rollback-on-error: "<true\|false>" }`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`cmdArgs: { tag: "<string>" }`	The tag identifying which tagged changesets in the changelog to evaluate. Specify as `--tag=myTag`. Positional format `<command> <tag>` deprecated in 4.4+.	Optional
`cmdArgs: { username: "<string>" }`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

Attribute	Definition	Requirement
`liquibase.command.changelogFile: <string>` `liquibase.command.updateTestingRollback.changelogFile: <string>`	The root changelog	Required
`liquibase.command.url: <string>` `liquibase.command.updateTestingRollback.url: <string>`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`liquibase.command.changeExecListenerClass: <string>` `liquibase.command.updateTestingRollback.changeExecListenerClass: <string>`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`liquibase.command.changeExecListenerPropertiesFile: <string>` `liquibase.command.updateTestingRollback.changeExecListenerPropertiesFile: <string>`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`liquibase.command.contextFilter: <string>` `liquibase.command.updateTestingRollback.contextFilter: <string>`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`liquibase.command.defaultCatalogName: <string>` `liquibase.command.updateTestingRollback.defaultCatalogName: <string>`	Name of the default catalog to use for the database connection	Optional
`liquibase.command.defaultSchemaName: <string>` `liquibase.command.updateTestingRollback.defaultSchemaName: <string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`liquibase.command.driver: <string>` `liquibase.command.updateTestingRollback.driver: <string>`	The JDBC driver class	Optional
`liquibase.command.driverPropertiesFile: <string>` `liquibase.command.updateTestingRollback.driverPropertiesFile: <string>`	The JDBC driver properties file	Optional
`liquibase.command.forceOnPartialChanges: <true\|false>` `liquibase.command.updateTestingRollback.forceOnPartialChanges: <true\|false>`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`liquibase.command.labelFilter: <string>` `liquibase.command.updateTestingRollback.labelFilter: <string>`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`liquibase.command.password: <string>` `liquibase.command.updateTestingRollback.password: <string>`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`liquibase.command.reportEnabled: <true\|false>` `liquibase.command.updateTestingRollback.reportEnabled: <true\|false>`	Enables a report at the command level. Overrides the global parameter `--reports-enabled`. Default: `true`.	Optional
`liquibase.command.reportName: <string>` `liquibase.command.updateTestingRollback.reportName: <string>`	Specifies the name of the report file at the command level. Overrides the global parameter `--reports-name`. By default, Liquibase generates a new report file labeled with a timestamp (user's local time). If you set a custom name, Liquibase overwrites the existing file every time you generate a new report. Default: `report-<DD-Mon-YYYY-HHmmss>.html`.	Optional
`liquibase.command.reportPath: <string>` `liquibase.command.updateTestingRollback.reportPath: <string>`	Specifies the file path to the report file at the command level. Overrides the global parameter `--reports-path`. Default: `./`.	Optional
`liquibase.command.reportSuppressException: <true\|false>` `liquibase.command.updateTestingRollback.reportSuppressException: <true\|false>`	Liquibase 4.31.0+. Specifies whether to hide exceptions (which may contain SQL) from the operation report at the command level. Overrides the global parameter `--reports-suppress-exception`. Default: `false`. However: If `--report-suppress-exception` is not set and `--report-suppress-sql=true`, Liquibase suppresses all SQL, including exception SQL. If `--report-suppress-exception=false` and `--report-suppress-sql=true`, Liquibase suppresses most SQL but shows exception SQL.	Optional
`liquibase.command.reportSuppressSql: <true\|false>` `liquibase.command.updateTestingRollback.reportSuppressSql: <true\|false>`	Liquibase 4.31.0+. Specifies whether to hide changeset SQL in operation reports at the command level. Overridden by the global parameter `--reports-suppress-sql`. Default: `false`.	Optional
`liquibase.command.rollbackOnError: <true\|false>` `liquibase.command.updateTestingRollback.rollbackOnError: <true\|false>`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`liquibase.command.tag: <string>` `liquibase.command.updateTestingRollback.tag: <string>`	The tag identifying which tagged changesets in the changelog to evaluate. Specify as `--tag=myTag`. Positional format `<command> <tag>` deprecated in 4.4+.	Optional
`liquibase.command.username: <string>` `liquibase.command.updateTestingRollback.username: <string>`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

Attribute	Definition	Requirement
`JAVA_OPTS=-Dliquibase.command.changelogFile=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.changelogFile=<string>`	The root changelog	Required
`JAVA_OPTS=-Dliquibase.command.url=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.url=<string>`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`JAVA_OPTS=-Dliquibase.command.changeExecListenerClass=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.changeExecListenerClass=<string>`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`JAVA_OPTS=-Dliquibase.command.changeExecListenerPropertiesFile=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.changeExecListenerPropertiesFile=<string>`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`JAVA_OPTS=-Dliquibase.command.contextFilter=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.contextFilter=<string>`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`JAVA_OPTS=-Dliquibase.command.defaultCatalogName=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.defaultCatalogName=<string>`	Name of the default catalog to use for the database connection	Optional
`JAVA_OPTS=-Dliquibase.command.defaultSchemaName=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.defaultSchemaName=<string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`JAVA_OPTS=-Dliquibase.command.driver=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.driver=<string>`	The JDBC driver class	Optional
`JAVA_OPTS=-Dliquibase.command.driverPropertiesFile=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.driverPropertiesFile=<string>`	The JDBC driver properties file	Optional
`JAVA_OPTS=-Dliquibase.command.forceOnPartialChanges=<true\|false>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.forceOnPartialChanges=<true\|false>`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`JAVA_OPTS=-Dliquibase.command.labelFilter=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.labelFilter=<string>`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`JAVA_OPTS=-Dliquibase.command.password=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.password=<string>`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`JAVA_OPTS=-Dliquibase.command.reportEnabled=<true\|false>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.reportEnabled=<true\|false>`	Enables a report at the command level. Overrides the global parameter `--reports-enabled`. Default: `true`.	Optional
`JAVA_OPTS=-Dliquibase.command.reportName=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.reportName=<string>`	Specifies the name of the report file at the command level. Overrides the global parameter `--reports-name`. By default, Liquibase generates a new report file labeled with a timestamp (user's local time). If you set a custom name, Liquibase overwrites the existing file every time you generate a new report. Default: `report-<DD-Mon-YYYY-HHmmss>.html`.	Optional
`JAVA_OPTS=-Dliquibase.command.reportPath=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.reportPath=<string>`	Specifies the file path to the report file at the command level. Overrides the global parameter `--reports-path`. Default: `./`.	Optional
`JAVA_OPTS=-Dliquibase.command.reportSuppressException=<true\|false>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.reportSuppressException=<true\|false>`	Liquibase 4.31.0+. Specifies whether to hide exceptions (which may contain SQL) from the operation report at the command level. Overrides the global parameter `--reports-suppress-exception`. Default: `false`. However: If `--report-suppress-exception` is not set and `--report-suppress-sql=true`, Liquibase suppresses all SQL, including exception SQL. If `--report-suppress-exception=false` and `--report-suppress-sql=true`, Liquibase suppresses most SQL but shows exception SQL.	Optional
`JAVA_OPTS=-Dliquibase.command.reportSuppressSql=<true\|false>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.reportSuppressSql=<true\|false>`	Liquibase 4.31.0+. Specifies whether to hide changeset SQL in operation reports at the command level. Overridden by the global parameter `--reports-suppress-sql`. Default: `false`.	Optional
`JAVA_OPTS=-Dliquibase.command.rollbackOnError=<true\|false>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.rollbackOnError=<true\|false>`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`JAVA_OPTS=-Dliquibase.command.tag=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.tag=<string>`	The tag identifying which tagged changesets in the changelog to evaluate. Specify as `--tag=myTag`. Positional format `<command> <tag>` deprecated in 4.4+.	Optional
`JAVA_OPTS=-Dliquibase.command.username=<string>` `JAVA_OPTS=-Dliquibase.command.updateTestingRollback.username=<string>`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

Attribute	Definition	Requirement
`LIQUIBASE_COMMAND_CHANGELOG_FILE=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_CHANGELOG_FILE=<string>`	The root changelog	Required
`LIQUIBASE_COMMAND_URL=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_URL=<string>`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`LIQUIBASE_COMMAND_CHANGE_EXEC_LISTENER_CLASS=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_CHANGE_EXEC_LISTENER_CLASS=<string>`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`LIQUIBASE_COMMAND_CHANGE_EXEC_LISTENER_PROPERTIES_FILE=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_CHANGE_EXEC_LISTENER_PROPERTIES_FILE=<string>`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`LIQUIBASE_COMMAND_CONTEXT_FILTER=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_CONTEXT_FILTER=<string>`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`LIQUIBASE_COMMAND_DEFAULT_CATALOG_NAME=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_DEFAULT_CATALOG_NAME=<string>`	Name of the default catalog to use for the database connection	Optional
`LIQUIBASE_COMMAND_DEFAULT_SCHEMA_NAME=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_DEFAULT_SCHEMA_NAME=<string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`LIQUIBASE_COMMAND_DRIVER=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_DRIVER=<string>`	The JDBC driver class	Optional
`LIQUIBASE_COMMAND_DRIVER_PROPERTIES_FILE=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_DRIVER_PROPERTIES_FILE=<string>`	The JDBC driver properties file	Optional
`LIQUIBASE_COMMAND_FORCE_ON_PARTIAL_CHANGES=<true\|false>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_FORCE_ON_PARTIAL_CHANGES=<true\|false>`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`LIQUIBASE_COMMAND_LABEL_FILTER=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_LABEL_FILTER=<string>`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`LIQUIBASE_COMMAND_PASSWORD=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_PASSWORD=<string>`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`LIQUIBASE_COMMAND_REPORT_ENABLED=<true\|false>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_REPORT_ENABLED=<true\|false>`	Enables a report at the command level. Overrides the global parameter `--reports-enabled`. Default: `true`.	Optional
`LIQUIBASE_COMMAND_REPORT_NAME=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_REPORT_NAME=<string>`	Specifies the name of the report file at the command level. Overrides the global parameter `--reports-name`. By default, Liquibase generates a new report file labeled with a timestamp (user's local time). If you set a custom name, Liquibase overwrites the existing file every time you generate a new report. Default: `report-<DD-Mon-YYYY-HHmmss>.html`.	Optional
`LIQUIBASE_COMMAND_REPORT_PATH=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_REPORT_PATH=<string>`	Specifies the file path to the report file at the command level. Overrides the global parameter `--reports-path`. Default: `./`.	Optional
`LIQUIBASE_COMMAND_REPORT_SUPPRESS_EXCEPTION=<true\|false>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_REPORT_SUPPRESS_EXCEPTION=<true\|false>`	Liquibase 4.31.0+. Specifies whether to hide exceptions (which may contain SQL) from the operation report at the command level. Overrides the global parameter `--reports-suppress-exception`. Default: `false`. However: If `--report-suppress-exception` is not set and `--report-suppress-sql=true`, Liquibase suppresses all SQL, including exception SQL. If `--report-suppress-exception=false` and `--report-suppress-sql=true`, Liquibase suppresses most SQL but shows exception SQL.	Optional
`LIQUIBASE_COMMAND_REPORT_SUPPRESS_SQL=<true\|false>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_REPORT_SUPPRESS_SQL=<true\|false>`	Liquibase 4.31.0+. Specifies whether to hide changeset SQL in operation reports at the command level. Overridden by the global parameter `--reports-suppress-sql`. Default: `false`.	Optional
`LIQUIBASE_COMMAND_ROLLBACK_ON_ERROR=<true\|false>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_ROLLBACK_ON_ERROR=<true\|false>`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`LIQUIBASE_COMMAND_TAG=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_TAG=<string>`	The tag identifying which tagged changesets in the changelog to evaluate. Specify as `--tag=myTag`. Positional format `<command> <tag>` deprecated in 4.4+.	Optional
`LIQUIBASE_COMMAND_USERNAME=<string>` `LIQUIBASE_COMMAND_UPDATE_TESTING_ROLLBACK_USERNAME=<string>`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

Note: The username and password attributes are not required for connections and systems which use alternate means of authentication. Also, you can specify database credentials as part of the url attribute.

Output

When successful, the update-testing-rollback command produces the following output:

Liquibase Version: 4.9.1
Liquibase Community 4.9.1 by Liquibase

Liquibase command 'update-testing-rollback' was executed successfully.

update-testing-rollback

Uses

Syntax

Command parameters

Output

Related links

`update-testing-rollback`