Thanks Bjorn for helping clarify that. I would take what you said a step
further by changing "could" to "must", since it appears that simply adding a
trigger back into a Jenkinsfile for a job that has run since the trigger was
removed, will necessarily have no effect until you manually run the j
Hi,
Am Freitag, 4. Oktober 2019 02:03:17 UTC+2 schrieb Tim Black:
>
> We have a multibranch pipeline job set up to scan a git repo (which
> contains Jenkinsfile at its root) for branches and create branch-specific
> jobs for each branch discovered. The Jenkinsfile on a branch specifies:
>
>
