[JIRA] (JENKINS-38075) Github Plugin build strategy improvement
Title: Message Title Kanstantsin Shautsou commented on JENKINS-38075 Re: Github Plugin build strategy improvement There are multiple separate plugins that has trigger features, githubpush trigger do what initial author did and behaviour can't be changed. Normally it should be named as GitHub gitscm poll trigger. If you want you can wait something in github-plugin but i guess nothing will be done in scope of this plugin because separate already existed. 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-38075) Github Plugin build strategy improvement
Title: Message Title Danny Cosson commented on JENKINS-38075 Re: Github Plugin build strategy improvement That's the whole point of this issue. Kicking off GitSCM.poll (especially if you know it's buggy) should not be the only option. This is a feature request to allow github to trigger a jenkins build directly via a github webhook. 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-38075) Github Plugin build strategy improvement
Title: Message Title Kanstantsin Shautsou commented on JENKINS-38075 Re: Github Plugin build strategy improvement new commits in PRs is not a github-plugin functionality or describe and provide configuration that you has to have any idea how reproduce your issue. 2) As it written in github-plugin docs, this plugin only kicks GitSCM.poll() so any (imho buggy) trigger/choose commit logic is git-plugin issue. You can also try to use other triggers i implemented experimental branch trigger in https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Integration+Plugin that kicks builds exactly for commits. 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-38075) Github Plugin build strategy improvement
Title: Message Title Kanstantsin Shautsou closed an issue as Not A Defect Jenkins / JENKINS-38075 Github Plugin build strategy improvement Change By: Kanstantsin Shautsou Status: Open Closed Resolution: Not A Defect 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-38075) Github Plugin build strategy improvement
Title: Message Title Kirill Merkushev commented on JENKINS-38075 Re: Github Plugin build strategy improvement What exact plugins list do you have? 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-38075) Github Plugin build strategy improvement
Title: Message Title Christian Stewart commented on JENKINS-38075 Re: Github Plugin build strategy improvement I have the same things happen... Also: new commits in PRs are not automatically built, the hook seems to be ignored I have to click "scan branches" pretty frequently 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-38075) Github Plugin build strategy improvement
Title: Message Title Danny Cosson created an issue Jenkins / JENKINS-38075 Github Plugin build strategy improvement Issue Type: Improvement Assignee: Kirill Merkushev Components: github-plugin Created: 2016/Sep/08 8:47 PM Environment: any Priority: Major Reporter: Danny Cosson The Github plugin has generally been very buggy for me, even on the latest version. The way I use it (which I think is very common, it's the way Travis and other hosted CI tools work by default) is with feature branches, to have Jenkins build every push to every branch on Github when it gets a webhook. The big issues I have are: 1. Every few days, it starts missing builds with no indication of what's going on. I see in the logs it gets the webhook pings from Github, but then it doesn't think there's anything to build. It sometimes fixes itself in an hour or two, or if I trigger a build manually that also fixes it. 2. There also seems to be a race condition where pushing branch A to github then pushing branch B shortly after can trigger a second build on branch A. In some cases, this seems to happen minutes after branch A has already completed, so I'm not sure it's actually a race condition. I haven't been able to reproduce this reliably or get much extra information. 3. When you first turn this on for a project, it builds all branches that exist on Github, many of which might be be on hold where there's really no need to build them right now at the expense of everything else. This swamps jenkins until they all complete. 4. Lastly, it doesn't work with the "rebuild" button plugin because the build is not parameterized, so rebuilding will rebuild whatever sha happened to run last, instead of rebuilding the sha of the run that you clicked "rebuild" on. These issues could presumably all be fixed
