Loading...

This issue is archived. You can view it, but you can't modify it. Learn more

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Minor
Component/s: workflow-multibranch-plugin
Labels:
- issue-exported-to-github

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

CloudBees Internal CD-38

(1 relates to, 1 links to)

Assignee:: Unassigned
Reporter:: Patrick Wolf

Created:: 2017-01-13 17:02
Updated:: 3 days ago 16:18
Archived:: 3 days ago 16:18

Details

Description

Attachments

Issue Links

Activity

People

Dates