Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41073

MultiBranch projects should veto SCM Polling

    XMLWordPrintable

Details

    Description

      As Branch API pins the SCM to the revision discovered by scanning / events, we should veto SCMTrigger polling of Multibranch child jobs

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-41146 SCM Trigger configuration being overwritten by SYSTEM user in Pipeline

          • Major - Major loss of function.
          • Resolved
          relates to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-32018 Multibranch workflow project tracking multiple repositories

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-40722 Poll SCM results in a Pipeline run every interval (unnecessarily)

          • Major - Major loss of function.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            stephenconnolly Stephen Connolly added a comment -

            Once JENKINS-32018 has a satisfactory implementation we can remove the block

            stephenconnolly Stephen Connolly added a comment - Once JENKINS-32018 has a satisfactory implementation we can remove the block
            stephenconnolly Stephen Connolly added a comment -

            Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

            stephenconnolly Stephen Connolly added a comment - Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

            People

              Unassigned Unassigned
              stephenconnolly Stephen Connolly
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: