...
On the packaging branch, find the commitID where the archive file was modified.
This commitID should be present in the log in the section PACKAGING ORDER FOR COMMIT FILES.
If there are changes after the above commitID dependent on changes between the last time Packager successfully packaged, just use the last commitID on the branch.
In the ddb repo, update the deployPackager.properties file <branch>.sqlScmLastImportID to use the commitID from step 1.
The existing <branch>.sqlScmLastImportID in the deployPackager.properties is the last time Packager ran successfully. This should also match the most recent “Datical automatic check-in” message if you are looking at the git commit log.
Run a Packaging job.
You will need to make small changes (eg. add a space) to any SQL files that were modified since the last time Packager ran successfully and the commitID you used in step 2 in order for Packager to pick up the changes and process them.
Commit these small changes to source control.
Run a Packaging job again to pick up the changes from all the SQL files modified in step 4.
| Info |
|---|
Note: This method is not recommended for projects with multiple pipelines that are merged into one branch from another, eg. develop → qa → stress → prod. In this case, each pipeline branch would need to have the sqlScmLastImportID updated after each merge from the lower branch until the problem was resolved across all pipelines. |
Method 2: Update the Packager branch to be based on commit prior to archive update
...