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

Workflow support for GitHub Push Triggers

    Details

    • Similar Issues:

      Description

      In continuation from https://issues.jenkins-ci.org/browse/JENKINS-26591 I'm also missing the gihub push triggers on the triggers section on the workflow job config page

        Attachments

          Issue Links

            Activity

            Hide
            lielran Liel Ran added a comment - - edited

            Thanks you - indeed important feature to the workflow, now the only part that is still missing is the support of the github pull requests...

            BTW- there is any workaround for the requirement of the first manual trigger in order that the plugin get hooks from github ?

            Show
            lielran Liel Ran added a comment - - edited Thanks you - indeed important feature to the workflow, now the only part that is still missing is the support of the github pull requests... BTW- there is any workaround for the requirement of the first manual trigger in order that the plugin get hooks from github ?
            Hide
            lionelve Lionel Orellana added a comment - - edited

            What about Multibranch Pipelines? The github push trigger is still missing there.

            Show
            lionelve Lionel Orellana added a comment - - edited What about Multibranch Pipelines? The github push trigger is still missing there.
            Hide
            amuniz Antonio Muñiz added a comment -

            There is not need for that trigger, github-branch-source-plugin covers that feature.

            Show
            amuniz Antonio Muñiz added a comment - There is not need for that trigger, github-branch-source-plugin covers that feature.
            Hide
            lionelve Lionel Orellana added a comment - - edited

            Thanks Antonio Muñiz. This might not be the right place but can you point me to some info on how to configure a Multibranch Pipeline to handle github webhooks. Thanks.

            Just found the 'Re-register hooks for all jobs' in the global config. That created the hooks correctly now. Thanks.

            Show
            lionelve Lionel Orellana added a comment - - edited Thanks Antonio Muñiz . This might not be the right place but can you point me to some info on how to configure a Multibranch Pipeline to handle github webhooks. Thanks. Just found the 'Re-register hooks for all jobs' in the global config. That created the hooks correctly now. Thanks.
            Hide
            b2yq Pawel Mucha added a comment - - edited

            1. In my scenario github-branch-source-plugi is getting timeouts on checkout, because is trying to make checkout with default values (10 min) on master, even if my pipeline script is using child node and has additional checkout configuration with increased time
            2. 'Re-register hooks for all jobs' only works if You have admin proviliges for git repo, and in my scenario I am using other company (client) repo, so I wont get it
            3. Please reopen this feature, because previous two solutions are not working in all cases

            Show
            b2yq Pawel Mucha added a comment - - edited 1. In my scenario github-branch-source-plugi is getting timeouts on checkout, because is trying to make checkout with default values (10 min) on master, even if my pipeline script is using child node and has additional checkout configuration with increased time 2. 'Re-register hooks for all jobs' only works if You have admin proviliges for git repo, and in my scenario I am using other company (client) repo, so I wont get it 3. Please reopen this feature, because previous two solutions are not working in all cases

              People

              • Assignee:
                amuniz Antonio Muñiz
                Reporter:
                s0undt3ch Pedro Algarvio
              • Votes:
                2 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: