-
Bug
-
Resolution: Unresolved
-
Minor
-
None
There is general confusing about how polling behaves in multibranch pipeline. Polling will continue to trigger the same revision over and over again because mutlibranch is pinned to the revision found in computation.
For now we should disable the trigger in properties step of a multibranch pipeline.
The recommendation for users not using webhooks would be to configure the "Periodically if not otherwise run" but this will add more api calls.
- depends on
-
JENKINS-19022 GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
- Open
- is duplicated by
-
JENKINS-44098 Multibranch branch is built twice, from branch indexing and scm change
- Resolved
- is related to
-
JENKINS-40722 Poll SCM results in a Pipeline run every interval (unnecessarily)
- Resolved
-
JENKINS-41072 Poll the GitHub Events API as an alternative to webhook
- Open
-
JENKINS-41146 SCM Trigger configuration being overwritten by SYSTEM user in Pipeline
- Resolved
- relates to
-
JENKINS-32018 Multibranch workflow project tracking multiple repositories
- Open
- links to