As our development teams move to Agile methodologies and automate their delivery processes, we DBAs need to be involved and included in this process. How do we automate our database schema and data changes and how do we insert them into the automated CI/CD pipelines? Database changes have unique challenges and requirements. For instance, they must be immutable, handled serially, cumulative, and usually must only be applied once. As an example, we will discuss using Liquibase to deploy and track Db2 LUW changes as part of a pipeline. We will discuss several issues that we have encountered in the past when doing manual and semi-automated deployments. These issues may include Error identification, handling, and determination (choosing to ignore Db2 errors and warnings that truly ok); rollbacks; schema version identification; and, running deployments multiple times. Then we will discuss how a tool like Liquibase can help solve these problems and allow us to better integrate our database changes into the process.