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

Trigger job when polling off if sha1 specified in push notification

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • git-plugin
    • None

      The documentation suggests that polling is not required when the "sha1" commitID param is given, so should it not be possible to trigger a build this way with polling turned off for the job? From testing it appears polling is still required in this case too.

      "Commit ID is optional. If set, it will immediately trigger a build, without requirement to poll for changes."

      I have > 100 Jenkins jobs I'd like to migrate to this style post-receive job trigger however having to modify the job configuration in this way for each one sounds like a very long afternoon.

          [JENKINS-28644] Trigger job when polling off if sha1 specified in push notification

          I seem to be asking for the opposite of JENKINS-26540 I think. Which makes me wonder why this isn't working for me. I'm using v2.3.5.

          Leif Gruenwoldt added a comment - I seem to be asking for the opposite of JENKINS-26540 I think. Which makes me wonder why this isn't working for me. I'm using v2.3.5.

          Mark Waite added a comment -

          You might attempt the same configuration with git plugin 2.3.4 rather than 2.3.5. There may have been regressions in the polling behavior in 2.3.5 which affected your use case.

          Mark Waite added a comment - You might attempt the same configuration with git plugin 2.3.4 rather than 2.3.5. There may have been regressions in the polling behavior in 2.3.5 which affected your use case.

          Mark Waite added a comment - - edited

          leif81 I read your bug report again and I think that the documentation needs to be made more clear.

          I think the behavior that I've seen has been that if a sha1= value is provided in the notify commit URL and if that sha1 exists in the repository and if polling is enabled for that job and if the "ignore post-commit hooks" check box is not checked, then a build will be started using that sha1.

          However, I'll need to perform more testing (and insert more tests into the git plugin test automation) before I can be sure of those statements.

          Mark Waite added a comment - - edited leif81 I read your bug report again and I think that the documentation needs to be made more clear. I think the behavior that I've seen has been that if a sha1= value is provided in the notify commit URL and if that sha1 exists in the repository and if polling is enabled for that job and if the "ignore post-commit hooks" check box is not checked, then a build will be started using that sha1. However, I'll need to perform more testing (and insert more tests into the git plugin test automation) before I can be sure of those statements.

            Unassigned Unassigned
            leif81 Leif Gruenwoldt
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: