I've setup a test with a repository that has several branches. I created a
freestyle jenkins job that uses Git SCM to checkout the repo. When I run
this job, it shows the below and results in multiple executions of the job:
Multiple candidate revisions
Scheduling another build to catch up with
branch
>
> Jenkins Pipeline allows you to define a multibranch pipeline so that
> Jenkins will automatically create a new job each time a branch is detected
> and will automatically destroy the job when a branch is deleted. That
> makes the history usable and simplifies the expe
t; Jenkins will automatically create a new job each time a branch is detected
>>> and will automatically destroy the job when a branch is deleted. That
>>> makes the history usable and simplifies the experience for users.
>>>
>>> On Tue, Oct 6, 2020 at 2:20 P