The docker-compose file will pull down and start a SQL Server container. From repo's root directory, execute:

docker-compose up

Once the SQL Server is running, you'll still need to create the database. Connect with the following info (also in the docker-compose file):

• username: sa
• password: DevOpsDaysP4ssword!
• server: localhost,1433
• trust server certificate: true

The DB Server will already have an initial DB, DevOpsDays, created via the Dockerfile.

A parent/master changelog (specified in liquibase.properties) will run child changelogs in the folder, changelogs in alphabetical order. From this directory, execute:

For Linux: ./Liquibase/liquibase update --defaultsFile="liquibase.properties" --log-file=logs/liquibase-update.log

For Windows: Liquibase\liquibase update --defaultsFile="liquibase.properties" --log-file=logs/liquibase-update.log

If you have just one changelog in this folder, it will execute.

You can create your own custom changelog to experiment, but you can also use the examples provided of well-formed and ill-formed changelogs.

Add these to the changelog folder and test the liquibase update command, the same as before for your OS.

'git add .' -> 'git commit –m “demo”' -> 'git push –u origin my-branch-name' Create the PR to merge into master and watch the validation flow in the “Actions” tab of the GitHub repository

No worries. We've included a basic script to delete most of the tables in the database, including the meta-tables for Liquibase. You can execute that and try again.