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

Poll the GitHub Events API as an alternative to webhook

    XMLWordPrintable

Details

    Attachments

      Issue Links

        is related to

        Bug - A problem which impairs or prevents the functions of the product. JENKINS-41074 UX Issue with Polling in Multibranch Pipeline

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Open

        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

        Bug - A problem which impairs or prevents the functions of the product. JENKINS-55949 Arrange RSS (or something like it) as a transport for GitHub webhooks

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • 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

        New Feature - A new feature of the product, which has yet to be developed. JENKINS-55993 Arrange GitHub email notifications support as an alternative transport for webhooks

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Open

        Activity

          Descending order - Click to sort in ascending order
          jimklimov Jim Klimov added a comment - - edited

          Linking to JENKINS-55949 as they seem to address a similar use-case. They are not duplicates, especially since the 55949 also touches on making a more generic solution than just one with GitHub, and it asks for persistent connection with server-side notifications coming in ASAP, while the Events API has to be polled regularly (though cheaply with regard to quota usage, if used with used with the ETag header and "304 Not Modified" response support).

          jimklimov Jim Klimov added a comment - - edited Linking to JENKINS-55949 as they seem to address a similar use-case. They are not duplicates, especially since the 55949 also touches on making a more generic solution than just one with GitHub, and it asks for persistent connection with server-side notifications coming in ASAP, while the Events API has to be polled regularly (though cheaply with regard to quota usage, if used with used with the ETag header and "304 Not Modified" response support).
          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:
            4 Start watching this issue

            Dates

              Created:
              Updated: