Page Comparison

...

We usually set up our build to be a multiple SCMs one. TO avoid to have to deal with passwords (you need to be sure you will not be queried for password or it will hung the job), we simply use the SSK key mechanism provided by GitHub.

SQL Repo

We also use 2 additional behaviors for that step:

1. check out to a sub-directory: portal_sql
2. Check out to specific local branch: 2017-2017july
3. (optional): Polling ignore commits from certain users:
   1. the idea behind this is simply to ignore changes create by the check in at the end of the packager. If you choose this option you will add your jenkins user in the "Excluded Users" field

That step should look like:

DaticalDB project repo

At the same level than the SQL repo, we have anothe repo that contains the DaticalDB project (this is where all you DB Refs are stored, as well as your pipeline information, the change sets, ...). This is the core DaticalDB.

 For this step as well, we use 3 additional behaviors for that step:

1. check out to a sub-directory: portal_ddb
2. Don't trigger a build on commit notification (if you have a CI, you do not want to start a new build when the DaticalDB project is modified)
3. Check out to specific local branch: master (as the chanes are cumulative, there is no need for a branch)

That step should look like:

Image Added

IBM uBuild

Atlassian Bamboo

...