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
Does unticking the option not work? If it doesn't then I'd consider raising
an issue against the plugin to track as that doesn't sound right.
Richard.
On Sat, 5 Oct 2019, 3:25 AM Andrey Kislyak, wrote:
> Hi All
>
> I have installed and configured bitbucket-branch-source-plugin v.2.4.0 on
> jenk
Hi All
I have installed and configured bitbucket-branch-source-plugin v.2.4.0 on
jenkins 2.176.2
On repository level exist option "Scan Multibranch Pipeline Triggers" once
a day.
How i can disable this trigger, plugin only view this config and does give
change.
--
You received this message be
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:
>
>
