[JIRA] (JENKINS-42020) branches to build specifier broken
Title: Message Title Neuronal T commented on JENKINS-42020 Re: branches to build specifier broken So, I may have chimed in on a thread where Ralph A's environment is centered on multi-branch and Pipeline Plugin usage. I'm not using Pipelines (yet; more of a team choice for that) and mine was a case specific to push event triggers from GitHub affecting branches with Multiple SCM Plugin, and the triggering of multiple branch build jobs. I isolated my situation (and wrote up a ticket here: Jenkins builds all jobs when user intends for one) around the behavior I saw. I'm open to understanding that we might have an ill-suited dev process for the way Jenkins functions with is SCM-push-trigger logic, but it seems to me that when a user commits a change to a branch, only that branch job should build, and not others (regardless if their GitHub state is a mismatch according to Jenkins). The "workaround" is that we use a single GitHub repo SCM with a submodule of the other GitHub repo that's needed (our jobs only had 2 repos). But since that 2nd repo is only needed for CI (and not dev work), this was an acceptable alternative. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42161) Jenkins builds all jobs when user intends for one
Title: Message Title Neuronal T created an issue Jenkins / JENKINS-42161 Jenkins builds all jobs when user intends for one Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 2017/Feb/17 7:57 PM Environment: Throwing in all versions that seem relevant, but I'm uncertain which codebases actually interact) Jenkins version 2.44 Multiple SCM Plugin 0.6 Git Client Plugin 2.2.1 Git Plugin 3.0.5 GitHub Integration Plugin 0.1.0-rc19 CentOS 6.7 Priority: Major Reporter: Neuronal T The issue is that Jenkins builds any job configured with a repo (using Multiple SCM Plugin) when that trigger event is confined to the BRANCH. The behavior should be that the SCM push event corresponds to the intended job that should be triggered AND ONLY that job. Instead, any job that was triggered/aborted in the quiet period gets triggered, so that it appears that all jobs for a repo are triggered. Set-up and reproduce: (This process assumes you've configured an OAUTH application secret, your Jenkins user to have GitHub access, Jenkins for GitHub webhook access, and vice versa) Set-up: -Create 2 GitHub repositories: buildtest and foo (initialized with README) -Configure their WebHook with http://your-jenkins-url:8080/github-webhook/, your secret text, etc. -Select Just the push event for the WebHook configuration -Add Jenkins user to Collaborators & Teams and give your Jenkins user Admin access to the buildtest1 and foo1 repositories -Create branches: buildtest with 1.1 and 5.0 branches, foo only has master -Create 4 Freestyle jobs with Git and Multiple SCM Plugin, selecting GitHub hook trigger for GITScm polling, configure 2 SCMs per job: +FOR ALL JOBS: Add SCM for foo and branch specifier: */master (branch specifier) for all jobs +1 job has second SCM as
[JIRA] (JENKINS-42155) Jenkins Multiple SCM Plugin causes all GitHub repository master/branch jobs to build
Title: Message Title Neuronal T closed an issue as Incomplete Jenkins / JENKINS-42155 Jenkins Multiple SCM Plugin causes all GitHub repository master/branch jobs to build Change By: Neuronal T Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42155) Jenkins Multiple SCM Plugin causes all GitHub repository master/branch jobs to build
Title: Message Title Neuronal T updated an issue Jenkins / JENKINS-42155 Jenkins Multiple SCM Plugin causes all GitHub repository master/branch jobs to build Change By: Neuronal T (This process assumes you've configured an OAUTH application secret, Jenkins for GitHub webhook access, and GitHub access to Jenkins)Run the following steps:-Create 2 GitHub repositories: buildtest1 and foo1 (initialized with README)-Configure their WebHook with http://your-jenkins-url:8080/github-webhook/, your secret text, etc.-Select Just the push event for the WebHook configuration -Add Jenkins user to Collaborators & Teams and give your Jenkins user Admin access to the buildtest1 and foo1 repositories-Create branches in both, respectively: 1.1, 5.0-Create Freestyle job with Git and Multiple SCM Plugin, selecting GitHub hook trigger for GITScm polling:+Add SCM for both buildtest1 and foo1, with */master as the branch.+ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this
[JIRA] (JENKINS-42155) Jenkins Multiple SCM Plugin causes all GitHub repository master/branch jobs to build
Title: Message Title Neuronal T created an issue Jenkins / JENKINS-42155 Jenkins Multiple SCM Plugin causes all GitHub repository master/branch jobs to build Issue Type: Bug Assignee: Kevin Bell Components: multiple-scms-plugin Created: 2017/Feb/17 5:47 PM Environment: Throwing in all versions that seem relevant, but I'm uncertain which codebases actually interact) Jenkins version 2.44 Multiple SCM Plugin 0.6 Git Client Plugin 2.2.1 Git Plugin 3.0.5 GitHub Integration Plugin 0.1.0-rc19 CentOS 6.7 Priority: Major Reporter: Neuronal T Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42020) branches to build specifier broken
Title: Message Title Neuronal T commented on JENKINS-42020 Re: branches to build specifier broken Ralph A, sorry to hear that. I'll also confirm that downgrading to Git Plugin 3.0.1 concluded with no change in brokenness (I also service-restarted Jenkins). In this case, for every branch I've created a job for a specific repo, there's a build being kicked off when I commit to a specific branch. Builds are kicked off for: 2.24.7 <-- change was committed here 2.30.1 master My team has another legacy cluster (Jenkins 1.625, Git Plugin 2.4.0) where this is not happening. Whether I keep or omit the refspec, change the branch-specifier to be accurate, etc., I can't, for the life of me, get the individual branch-job combination. Is there something I am missing, as far as setting up a filter for the github webhook? Should the payload be modified some how - I'm not sure how to do this with GitHub Plugin and the Git Webhook still does a push event, but doesn't filter what's in the payload without a post receive hook. I was really hoping to avoid going down this path.. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42020) branches to build specifier broken
Title: Message Title Neuronal T commented on JENKINS-42020 Re: branches to build specifier broken Thanks for your insight, Ralph A. Did you try downgrading Git Plugin to 3.0.1 and retry? I'm thinking to stepwise/trial-and-error downgrade plugin versions until this works.. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42020) branches to build specifier broken
Title: Message Title Neuronal T edited a comment on JENKINS-42020 Re: branches to build specifier broken I'm having a similar, and extremely frustrating time with this. I'm probably being really stupid, so I'm happy to be educated and corrected to get this working.The problem I'm encountering is that jobs that are confined to a specific branch specifier/refspec are kicked off no matter which branch was committed to in GIT. My configuration is this: Jenkins 2.44java- 1 .8.0-openjdk-1.8.0.121-0.b13.el6_8.x86_641 ) create a Jenkins/Freestyle Job/Git configured/branch combo: g...@github.foo.com:org/repo.gitrefspec: +refs/heads/2.24.7:refs/remotes/origin/2.24.7branch specifier: 2.24.7 (also tested with refs/heads/2.24.7)2) create a Jenkins/Freestyle Job/Git configured/master combo: g...@github.foo.com:org/repo.gitrefspec: +refs/heads/master:refs/remotes/origin/masterbranch specifier: master3) Set the trigger in each job: GitHub hook trigger for GITScm polling4) git clone g...@github.foo.com:org/repo.git && # modify a file in your repo, then do a git commit -m file BRANCH, and then 5) Tail the jenkins.log, to watch the aggravation happen:INFO: Received PUSH for https://github.foo.com/orgfoo/buildtest1 from 18.121.155.200 ⇒ http://foo.build.iwefjiwfj.com:12031/github-webhook/Feb 14, 2017 1:22:14 PM com.cloudbees.jenkins.GitHubPushTrigger$1 runINFO: SCM changes detected in buildtest-master. Triggering #4Feb 14, 2017 1:22:14 PM com.cloudbees.jenkins.GitHubPushTrigger$1 runINFO: SCM changes detected in buildtest-2.24-only. Triggering #2Why?? Why is this triggering a master build when I performed my actions solely on the 2.24.7 branch? I must have configured something wrong (like the endpoint URL) or something in GitHub.. The webhook is configured only for push events. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42020) branches to build specifier broken
Title: Message Title Neuronal T commented on JENKINS-42020 Re: branches to build specifier broken I'm having a similar, and extremely frustrating time with this. I'm probably being really stupid, so I'm happy to be educated and corrected to get this working. The problem I'm encountering is that jobs that are confined to a specific branch specifier/refspec are kicked off no matter which branch was committed to in GIT. My configuration is this: 1) create a Jenkins/Freestyle Job/Git configured/branch combo: g...@github.foo.com:org/repo.git refspec: +refs/heads/2.24.7:refs/remotes/origin/2.24.7 branch specifier: 2.24.7 (also tested with refs/heads/2.24.7) 2) create a Jenkins/Freestyle Job/Git configured/master combo: g...@github.foo.com:org/repo.git refspec: +refs/heads/master:refs/remotes/origin/master branch specifier: master 3) Set the trigger in each job: GitHub hook trigger for GITScm polling 4) git clone g...@github.foo.com:org/repo.git && # modify a file in your repo, then do a git commit -m file BRANCH, and then 5) Tail the jenkins.log, to watch the aggravation happen: INFO: Received PUSH for https://github.foo.com/orgfoo/buildtest1 from 18.121.155.200 ⇒ http://foo.build.iwefjiwfj.com:12031/github-webhook/ Feb 14, 2017 1:22:14 PM com.cloudbees.jenkins.GitHubPushTrigger$1 run INFO: SCM changes detected in buildtest-master. Triggering #4 Feb 14, 2017 1:22:14 PM com.cloudbees.jenkins.GitHubPushTrigger$1 run INFO: SCM changes detected in buildtest-2.24-only. Triggering #2 Why?? Why is this triggering a master build when I performed my actions solely on the 2.24.7 branch? I must have configured something wrong (like the endpoint URL) or something in GitHub.. The webhook is configured only for push events. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
