...
If a developer has checked-in a file that causes a packaging error for a particular branch, that branch/pipeline is essentially blocked until the developer fixes the script causing the error. Dynamic branch names allow another team or individual to package their changes using a different code branch even if another branch has an error.
Scenario 3: Teams want to test their changes prior to check-in to a shared branch
If you wish to provide an avenue for teams to validate their SQL changes prior to check-in to a shared or protected branch you may wish to consider using dynamic branch names.
\uD83D\uDCD8 Instructions
...
The deployPackager.properties is configured with the sqlScmLastImportID from main branch.
Branch_A is created from main branch.
Branch_B is created from main branch.
Branch_A packages successfully and the deployPackager.properties is updated by Liquibase Enterprise with a new sqlScmLastImportID located on Branch_A.
Branch_B does not have the new sqlScmLastImportID directly in it’s git commit history, but this commit can be located by git log because it shares a common ancestor.
Git command
The git command used to get the history of commits on a branch is below.
git log --reverse --pretty=format:'%h, %an, %s' --abbrev-commit <sqlScmLastImportID>..HEAD
By default, git log collects all commits starting from the current branch tip and traverses back through all ancestors. It will return all reachable commits in the current branch’s history.
\uD83D\uDCCB Related articles
...