-
Improvement
-
Resolution: Unresolved
-
Minor
-
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
Description |
Original:
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 eachone sounds like a very long afternoon. |
New:
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. |
Workflow | Original: JNJira [ 163497 ] | New: JNJira + In-Review [ 181262 ] |
Assignee | Original: Nicolas De Loof [ ndeloof ] |
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.