Thanks for the reply Mark. After posting the question, I started looking
at the builds folders within the jobs and each build has a changelog which
has a 'tree' in it. I assume Jenkins will use that 'tree' to figure out
the changes between branches? Just guessing.
I also ran some test
"Mark Waite" wrote:
> The multi-branch freestyle job type and the multibranch pipeline job type
> will automatically create and delete a job for each branch that matches your
> selection criteria.
> I very much prefer a job per branch because it makes the changes
On Monday, September 19, 2016 at 3:59:15 PM UTC-7, Sam K wrote:
>
> How will it affect the list of changes it shows on the builds page?
>
> Build No. 10 was built with master branch
> Build No. 11 is built with release_alpha branch
> Build No. 12 is then built with master branch
>
> Will
How will it affect the list of changes it shows on the builds page?
Build No. 10 was built with master branch
Build No. 11 is built with release_alpha branch
Build No. 12 is then built with master branch
Will changes between the builds be tracked correctly? Will build no. 12
report changes