Contexts in Liquibase are expressions you can add to changesets to control which will be executed in any particular migration run. Any string can be used for the context name and they are checked case-insensitively.
When you run the migrator though any of the available methods, you can pass in a set of contexts to run. Only changesets marked with the passed contexts will be run.
If you don’t assign a context to a changeset, it will run all the time, regardless of what contexts you pass in to the migrator.
If you do not specify a context when you run the migrator, ALL contexts will be run.
Here is an example of a changeset using the context attribute:
Contexts can be specified using AND, OR, ! and parentheses. Without parentheses the order of operations are “!” then “AND” then “OR”.
- context=”v1.0 or map”
- context=”v1.0 or map”
- context=”!qa and !master”
Using a “,” to separate contexts works like an OR operation but with the highest precedence.
- “test, qa” is the same as “test OR qa”
- “test, qa and master” is the same as “(test) OR (qa and master)
- ”,” separator available in all versions of Liquibase
- “AND, OR, !, parentheses” added in 3.2.0
Using contexts for test data
If you are managing your test data with Liquibase, the best way to include it is in-line with all your other changesets, but marked with a “test” context. That way, when you want your test data inserted you can run the migrator with the “test” context. When it comes time to migrate your production database, don’t include the “test” context, and your test data will not be included (bare in mind that if you do not specify any context at all, every changeset will be applied, including those marked with a “test” context). If you have multiple test environments or test data sets, simply tag them with different contexts such as “min-test”, “integration-test”, etc.
Using contexts to control test data is better than having a separate changelogs tree because later Change Types and changes will be applied to existing test data the same as they are applied to production data. If you had a set of test data that was created and simply added after the database is set up, you would be constantly manually updating your test data scripts to keep them in line with the current database schema.
Using contexts for multi-DBMS changelogs
You can use contexts to control which changesets run on which databases, but the better option is to use the built-in “dbms” tag on the changeset tag.
Beginning with Liquibase 3.5, you can specify a context attribute in the root DATABASECHANGELOG node to assign that context to all changesets in the changelog by default.
The specified context will be AND’ed with any contexts specified in changesets within the changelog file.
Beginning with Liquibase 3.5, you can specify a context attribute in
<includeAll> tags. If specified, the given context is added to all changesets in the included file(s).