...
- CLI - Add Labels: You will first add November label "nov_release" to all October changes
- use "hammer addLabels" command to add labels to October changes
Here is the help for "hammer addLabels" command
Code Block language bash firstline 1 title addLabels help linenumbers true collapse true USAGE: addLabels --lookupChangesets=<label expression> --labels=<comma separated list of labels to add> --scriptChecksum=<SQL script checksum value> --matchAll=<true/false>Options: lookupChangesets - Expression used to match the change sets (required) labels - Comma-separated list of labels (required) scriptChecksum - SQL script checksum value matchAll - SQL Script checksums must match for change set lookup. Default value is true
- For our example, use this command to add "nov_release" label to October changes:
hammer addLabels --lookupChangesets="oct_release" --labels="nov_release"
- Successful completion of this command generates the following output:
Code Block language bash firstline 1 title addLabels linenumbers true collapse true C:\Users\Datical\datical\DDBProject>hammer addLabels --lookupChangesets="oct_release" --labels="nov_release" Updating labels for change set j6fm-1 (createTable tableName=AAA_TESTA1) Updating labels for change set jvrp-1 (createTable tableName=AAA_TESTA2) Updating labels for change set 20170714131141429_Insert_dml_AAA_TESTA1 Updating labels for change set 20170714131141461_Insert_dml_AAA_TESTA2 Updating labels for change set AutoPermissions_PPADM_Tables C:\Users\Datical\datical\DDBProject>
You have now successfully added "nov_release" label to all October changes.
- use "hammer addLabels" command to add labels to October changes
- CLI - Deploy: Now deploy October changes into Pipeline 2 using "hammer" command
- You can now Forecast on REF2.
- Use "hammer forecast" command
Here is the help for "hammer forecast" command
Code Block language bash firstline 1 title forecast help linenumbers true collapse true C:\Users\Datical\datical\DDBProject>hammer help forecast forecast - Simulates all change sets that have not been applied to the indicated database reference. USAGE: forecast <dbref> [--log=/path/to/log] [--report=/path/to/report] [--context=context1,context2] [--labels=<label expression>] EXAMPLE: forecast myAppDevDb --log=/home/user/logs/ --report=/home/user/reports --context=dev,qa --labels="JUN AND (poolApp or beachApp)" OPTIONAL PARAMETERS: --log - Location to write the daticaldb.log file. Log is written to 'Logs' directory of project by default. --report - Location to write the forecast report. Report is written to the 'Reports' directory by default. --context - Only change sets marked with the contexts specified will be executed. To run all contexts, specify $all. --labels - When set, only change sets marked with the label expression will be executed. To run all labels, specify $all. C:\Users\Datical\datical\DDBProject>
For our example, use this command to forecast "nov_release" label to October changes:
hammer forecast REF2 --labels="nov_release"
- Successful completion of this command generates the following output:
Code Block language bash firstline 1 title addLabels linenumbers true collapse true C:\Users\Datical\datical\DDBProject>hammer forecast REF2 --labels="nov_release" There were no rules files found. Defaulting contexts to REF2 from REF2 Defaulting to database definition contexts of 'REF2' There are 5 change sets forecast to be deployed using labels 'nov_release' and contexts 'ref2' Report ready at C:\Users\Datical\datical\DDBProject\Reports\2017\07-Jul\REF2\forecast_REF2_20170724_152507\forecastReport.html C:\Users\Datical\datical\DDBProject>
- You have now successfully backfilled October changes into REF2 database.
Repeat steps 2a-2b to backfill DEV2 and QA2 databases.
- You can now Forecast on REF2.
Step-by-step guide (Using Datical DB GUI)
...