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

Poll the GitHub Events API as an alternative to webhook

    XMLWordPrintable

    Details

    • Similar Issues:

      Attachments

        Issue Links

          Activity

          Hide
          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

          Show
          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
          Hide
          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).

          Show
          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).

            People

            • Assignee:
              Unassigned
              Reporter:
              stephenconnolly Stephen Connolly
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: