[JIRA] (JENKINS-50522) New jobs not validating github webhook filters
Title: Message Title Byron Kim commented on JENKINS-50522 Re: New jobs not validating github webhook filters Kirill Merkushev - I've done a bunch of testing and the behavior is seemingly random. I even tried running this locally from the official Jenkins container from scratch, install all relevant plugins, taking a sample Github payload and posting to my local container and it's triggering the build. The sample payload was changes set to push to a branch called integration and my projects were set to only trigger a build on branch master The behavior is seemingly random on my production container. Some old projects are fulfilling the filters while mostly new ones are not. Please let me know if you need any other information. STEPS TO REPRODUCE: 1. docker run -d -p 8080:8080 jenkins/jenkins:lts 2. Install Git/Github plugins 3. Create a project and select Github project and enable GitHub hook trigger for GITScm polling. Configure auth for Github (ie SSH key or username/password) 4. Set Branch Specifier (blank for 'any') to "./random" 5. Create a branch with (not "random") and push something. Grab payload and copy to test.json 6. Post to local container: curl -v POST localhost:8080/github-webhook/ -d @test.json -H "Content-Type: application/json" -H "X-Github-Event: push" If you want to see the behavior repeat, you need to update the payload with a new one. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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+unsub
[JIRA] (JENKINS-50522) New jobs not validating github webhook filters
Title: Message Title Byron Kim created an issue Jenkins / JENKINS-50522 New jobs not validating github webhook filters Issue Type: Bug Assignee: Kirill Merkushev Components: github-branch-source-plugin, github-plugin Created: 2018-04-02 17:21 Environment: Jenkins ver. 2.89.4 Github Branch Source Plugin: 2.3.3 Github Plugin: 1.29.0 Labels: scm plugin jenkins Priority: Major Reporter: Byron Kim We have a Github repo that can trigger multiple builds based on certain filters. The most obvious one is the branch and then some are filtered down based on the Included Regions filter (ie Jenkins is triggered based on which path files are committed to). As an example: App-AuthAPI App-LookupAPI App-DBAPI Each one is from the same repo however, App-DBAPI was added recently and is triggered no matter what happens (random branch is deleted, a commit to a completely different branch). I have a test build that I modified and that worked fine based on filters. When I created anything new, none of the filters are respected. I restarted Jenkins and the filters are fine for about 10 minutes before it goes back to triggering for every event in the repo. I've tested cloning projects, to recreating from scratch, to doing the most basic thing (ie random string branch that doesn't actual
[JIRA] [workflow-plugin] (JENKINS-34353) No Source Code Management option in Pipeline
Title: Message Title Byron Kim edited a comment on JENKINS-34353 Re: No Source Code Management option in Pipeline [~jglick] I already have that plugin installed. See my screenshot. I don't have any SCM options for the build trigger. !http://i.imgur.com/6eMgKWj.png![~integer] you obviously still care Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-34353) No Source Code Management option in Pipeline
Title: Message Title Byron Kim commented on JENKINS-34353 Re: No Source Code Management option in Pipeline Jesse Glick I already have that plugin installed. See my screenshot. Kanstantsin Shautsou you obviously still care Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-34353) No Source Code Management option in Pipeline
Title: Message Title Byron Kim commented on JENKINS-34353 Re: No Source Code Management option in Pipeline I dunno if I'm not making myself clear or I'm missing something completely obvious. I don't have a SCM option so that when a commit is pushed to a branch in Github, it will trigger a webhook. You can see the option in Tomasz Przybysz screenshot. I have that in a regular job, but not a pipeline job. I want Jenkins to trigger the build when a push is commited to Github. The checkbox is available, but I do *not* have an option to select the branch or the repo for that matter. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-integration-plugin] (JENKINS-34353) No Source Code Management option in Pipeline
Title: Message Title Byron Kim reopened an issue Hello, this is not a duplicate issue to the one you linked in the comments. This is an issue of not seeing SCM at all in Jenkins Pipeline. I want the Github webhook to trigger pipeline, but I do not have this option. Again, I'm not referring to the Pipeline script options. Jenkins / JENKINS-34353 No Source Code Management option in Pipeline Change By: Byron Kim Resolution: Duplicate Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-integration-plugin] (JENKINS-34353) No Source Code Management option in Pipeline
Title: Message Title Byron Kim commented on JENKINS-34353 Re: No Source Code Management option in Pipeline Sorry - it is American way of emphasizing a point. I have the Github webhook setup and in a regular build, any time a commit happens to a branch in Github, it will trigger the Jenkins job. In pipeline, I do not have this option. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-integration-plugin] (JENKINS-34353) No Source Code Management option in Pipeline
Title: Message Title Byron Kim commented on JENKINS-34353 Re: No Source Code Management option in Pipeline Hi - my issue is I want to be able to run the pipeline from a Github trigger. I'm not even talking about the pipeline script. I just want to be able to use the Github webhook to trigger the build period. I don't have this option. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-integration-plugin] (JENKINS-34353) No Source Code Management option in Pipeline
Title: Message Title Byron Kim created an issue Jenkins / JENKINS-34353 No Source Code Management option in Pipeline Issue Type: Bug Assignee: Kanstantsin Shautsou Components: github-integration-plugin, github-plugin Created: 2016/Apr/20 6:26 PM Environment: 2.0-beta-2 All latest version of plugins installed Priority: Minor Reporter: Byron Kim I am new to Jenkins and created a job that would build based on the Github trigger. I was able to set this up so when a commit is pushed to Github, it would trigger builds on certain branches. I'm now trying to convert this build into a pipeline and do not see the Source Code Management option in Pipelines. I have the ability to check 'Build when a change is pushed to GitHub' but no option to select the Github repository. I saw Pipelines has a "Pipeline script from SCM" but that doesn't seem to work based on a trigger from Github.
