-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
kubernetes, amazon-linux, jenkins-war:2.190.3
When using "GitHub hook trigger for GITScm polling" all repos which are cloned either by checkout or git a push in one of them will triggered the build by hook. (pipline)
but if I want any of them not to trigger the build and I set the configuration
checkout changelog: false, poll: false, ....
it is still triggering the build.
found some workaround, see link
It is duplicate of https://issues.jenkins-ci.org/browse/JENKINS-44426, Can close this one
- duplicates
-
-
- Open
-
[JENKINS-60739] Github hook and trigger created even if repo checkout configured "poll = false"
| Description |
Original:
When using "GitHub hook trigger for GITScm polling" all repos which are cloned either by checkout or git a push in one of them will triggered the build by hook. (pipline) but if I want any of them not to trigger the build and I set the configuration checkout changelog: false, poll: false, .... it is still triggering the build. |
New:
When using "GitHub hook trigger for GITScm polling" all repos which are cloned either by checkout or git a push in one of them will triggered the build by hook. (pipline) but if I want any of them not to trigger the build and I set the configuration checkout changelog: false, poll: false, .... it is still triggering the build. found some workaround, see [link|[https://stackoverflow.com/questions/33792633/using-jenkins-job-dsl-to-set-polling-ignores-commits-in-certain-paths-for-git]] |
| Description |
Original:
When using "GitHub hook trigger for GITScm polling" all repos which are cloned either by checkout or git a push in one of them will triggered the build by hook. (pipline) but if I want any of them not to trigger the build and I set the configuration checkout changelog: false, poll: false, .... it is still triggering the build. found some workaround, see [link|[https://stackoverflow.com/questions/33792633/using-jenkins-job-dsl-to-set-polling-ignores-commits-in-certain-paths-for-git]] |
New:
When using "GitHub hook trigger for GITScm polling" all repos which are cloned either by checkout or git a push in one of them will triggered the build by hook. (pipline) but if I want any of them not to trigger the build and I set the configuration checkout changelog: false, poll: false, .... it is still triggering the build. found some workaround, see [link|https://issues.jenkins-ci.org/browse/JENKINS-44426] |
| Description |
Original:
When using "GitHub hook trigger for GITScm polling" all repos which are cloned either by checkout or git a push in one of them will triggered the build by hook. (pipline) but if I want any of them not to trigger the build and I set the configuration checkout changelog: false, poll: false, .... it is still triggering the build. found some workaround, see [link|https://issues.jenkins-ci.org/browse/JENKINS-44426] |
New:
When using "GitHub hook trigger for GITScm polling" all repos which are cloned either by checkout or git a push in one of them will triggered the build by hook. (pipline) but if I want any of them not to trigger the build and I set the configuration checkout changelog: false, poll: false, .... it is still triggering the build. found some workaround, see link It is duplicate of https://issues.jenkins-ci.org/browse/JENKINS-44426 |
| Description |
Original:
When using "GitHub hook trigger for GITScm polling" all repos which are cloned either by checkout or git a push in one of them will triggered the build by hook. (pipline) but if I want any of them not to trigger the build and I set the configuration checkout changelog: false, poll: false, .... it is still triggering the build. found some workaround, see link It is duplicate of https://issues.jenkins-ci.org/browse/JENKINS-44426 |
New:
When using "GitHub hook trigger for GITScm polling" all repos which are cloned either by checkout or git a push in one of them will triggered the build by hook. (pipline) but if I want any of them not to trigger the build and I set the configuration checkout changelog: false, poll: false, .... it is still triggering the build. found some workaround, see link It is duplicate of https://issues.jenkins-ci.org/browse/JENKINS-44426, Can close this one |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Fixed but Unreleased [ 10203 ] |
| Resolution | Original: Duplicate [ 3 ] | |
| Status | Original: Fixed but Unreleased [ 10203 ] | New: Reopened [ 4 ] |
| Link | New: This issue duplicates JENKINS-44426 [ JENKINS-44426 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Reopened [ 4 ] | New: Fixed but Unreleased [ 10203 ] |