...
The normal release workflow allows you to deploy and roll back changesets throughout a project pipeline. Rollbacks can be automatic for some changes or be performed by custom rollback scripts you supply. See /wiki/spaces/DDOC59/pages/795673649Rolling Back Changes.
However, the development workflow is for making changes to the changesets (and other changesets they affect). When you use the -ignore, -cleanup, and -replace scripts, they mark the original changesets so that they are no longer deployed. Changes are anticipated at these stages in a pipeline. They are not expected in later stages.
...
invoice_columns.sqlinvoice_columns-ignore.sql or invoice_columns_ignore.sql
When invoice_columns-ignore.sql or invoice_columns_ignore.sql is processed, the ignore attribute is set on all of the original changesets produced by invoice_columns.sql. The changesets are no longer deployed.
| Note |
|---|
Do not use more than one suffix when working in a development workflow (-ignore, -unignore, -replace, -cleanup, -rollback). For example, when you update a |
| Note |
|---|
It is important to maintain consistent case in workflow file names!When creating a new workflow file it is important to maintain file name casing that is consistent with the original file. If you are using git, you may have to run the following command to configure your repository to enforce consistent file name case: |