| Table of Contents |
|---|
...
For the purpose of the document, we will assume that the Datical project has the following pipeline and that all changesets generating from "temp_table.sql" were previously abandoned for release 1.0.0. And prior to getting abandoned, those changes had been deployed up until the QA environment. We now need to unabandon changesets from this script so that those can be deployed to STAGE and PROD environments as part of release 2.0.0. As such, you will remove the label "abandoned" from those changesets. And you will add the new label for the release (release/2.0.0).
REF1 | DEV | QA | STAGE | PROD | |
|---|---|---|---|---|---|
| Changesets from "temp_table.sql" | DEPLOYED | DEPLOYED | DEPLOYED | ABANDONED | ABANDONED |
| Initial labels | temp_table.sql,release/1.0.0,abandoned | ||||
| Final labels | temp_table.sql,release/1.0.0,release/2.0.0 | ||||
You can perform this task in automation, however, the user will need to provide two input parameters: 1) the script name to unabandon and 2) the new release label. In your automation system (Jenkins, Bamboo, UrbanCode Build, etc.), create a new job which will perform following operations:
...
hammer deploy STAGE --labels "release/2.0.0 AND !abandoned"hammer deploy PROD --labels "release/2.0.0 AND !abandoned"
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...