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.
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.
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://stackoverflowissues.comjenkins-ci.org/questionsbrowse/33792633/usingJENKINS-jenkins-job-dsl-to-set-polling-ignores-commits-in-certain-paths-for-git44426]]
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.
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.