[JIRA] (JENKINS-57116) Version 1.15.1 does not create pods
Title: Message Title Josh Chandler commented on JENKINS-57116 Re: Version 1.15.1 does not create pods First line of config.xml: '1.1' encoding='UTF-8'?> I'm not seeing any yaml in my podTemplate; here's what I've got in config.xml: jnlp-buildpod ci false false false 10 600 30 0 ops-jenkins NORMAL false "org.csanchez.jenkins.plugins.kubernetes.volumes.workspace.EmptyDirWorkspaceVolume"> false /var/run/docker.sock /var/run/docker.sock docker docker:18.09.1-dind true false /home/jenkins /bin/sh -c cat true 500m 1Gi 1 2Gi 0 0 0 0 0 kubectl lachlanevenson/k8s-kubectl:v1.10.12 false false /home/jenkins /bin/sh -c cat true 100m 500Mi 100m 500Mi 0 0 0 0 0 cmdtools alpine:3.8 false false /home/jenkins /bin/sh -c cat true 100m 100Mi 100m 100Mi 0 0 0 0 0 cmdtools-python python:3.6.7 false false /home/jenkins /bin/sh -c cat true 0 0 0 0 0 cmdtools-centos centos:7.6.1810 false false /home/jenkins /bin/sh -c cat true 0 0 0 0 0 "org.csanchez.jenkins.plugins.kubernetes.pod.retention.Default"/> Add Comment
[JIRA] (JENKINS-57116) Version 1.15.1 does not create pods
Title: Message Title Josh Chandler assigned an issue to Josh Chandler Jenkins / JENKINS-57116 Version 1.15.1 does not create pods Change By: Josh Chandler Assignee: Carlos Sanchez Josh Chandler Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-57116) Version 1.15.1 does not create pods
Title: Message Title Josh Chandler assigned an issue to Carlos Sanchez Jenkins / JENKINS-57116 Version 1.15.1 does not create pods Change By: Josh Chandler Assignee: Josh Chandler Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-57116) Version 1.15.1 does not create pods
Title: Message Title Josh Chandler commented on JENKINS-57116 Re: Version 1.15.1 does not create pods 1) Declarative pipelines in general. 2) For me, Jenkins admin to define the pod template. 3) Not using yaml - all within the admin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-57116) Version 1.15.1 does not create pods
Title: Message Title
Josh Chandler edited a comment on JENKINS-57116
Re: Version 1.15.1 does not create pods
I experienced this problem with 1.15.2; a rollback to 1.14.9 does fix the issue. My log output regarding the issue at hand is exactly the same as [~mreinhardt]. The plugin will try to create a pod, fail on that error, fail to delete the pod (as it never existed in the first place), and tries all of that over again. A log recorder on *org.csanchez.jenkins.plugins.kubernetes* provided no more logs than watching Jenkins' own output.Versions, pod definition, and pipeline below. Not sure if this is what you're looking for exactly [~csanchez] - will be happy to provide more as you require.Jenkins version: 2.162Kubernetes Version: v1.12.6-gke.10 Kubernetes plugin version (since rolled back): 1.15.2 GKE OS Version: Container-Optimized OS (latest as of 2019-04-29)Pod template:{code:java}$ kubectl get pods --export -o yaml jnlp-buildpod-cgpfmapiVersion: v1kind: Podmetadata: creationTimestamp: null labels:jenkins: slave name: jnlp-buildpod-cgpfm selfLink: /api/v1/namespaces/ci/pods/jnlp-buildpod-cgpfmspec: containers: - args:- catcommand:- /bin/sh- -cenv:- name: JENKINS_SECRET value: [redacted] - name: JENKINS_AGENT_NAME value: jnlp-buildpod-cgpfm- name: JENKINS_NAME value: jnlp-buildpod-cgpfm- name: JENKINS_URL value: http://ops-jenkins.ci.svc.cluster.local:8080/- name: HOME value: /home/jenkinsimage: centos:7.6.1810imagePullPolicy: IfNotPresentname: cmdtools-centosresources: {}securityContext: privileged: false procMount: DefaultterminationMessagePath: /dev/termination-logterminationMessagePolicy: Filetty: truevolumeMounts:- mountPath: /var/run/docker.sock name: volume-0- mountPath: /home/jenkins name: workspace-volume- mountPath: /var/run/secrets/kubernetes.io/serviceaccount name: ops-jenkins-token-2dszv readOnly: trueworkingDir: /home/jenkins - args:- catcommand:- /bin/sh- -cenv:- name: JENKINS_SECRET value: [redacted]- name: JENKINS_AGENT_NAME value: jnlp-buildpod-cgpfm- name: JENKINS_NAME value: jnlp-buildpod-cgpfm- name: JENKINS_URL value: http://ops-jenkins.ci.svc.cluster.local:8080/- name: HOME value: /home/jenkinsimage: alpine:3.8imagePullPolicy: IfNotPresentname: cmdtoolsresources: limits:cpu: 100mmemory: 100Mi requests:cpu: 100mmemory: 100MisecurityContext: privileged: false procMount: DefaultterminationMessagePath: /dev/termination-logterminationMessagePolicy: Filetty: truevolumeMounts:- mountPath: /var/run/docker.sock name: volume-0- mountPath: /home/jenkins name: workspace-volume- mountPath: /var/run/secrets/kubernetes.io/serviceaccount name: ops-jenkins-token-2dszv readOnly: trueworkingDir: /home/jenkins - args:- catcommand:- /bin/sh- -cenv:- name: JENKINS_SECRET value: [redacted] - name: JENKINS_AGENT_NAME value: jnlp-buildpod-cgpfm- name: JENKINS_NAME value: jnlp-buildpod-cgpfm- name: JENKINS_URL value: http://ops-jenkins.ci.svc.cluster.local:8080/- name: HOME value: /home/jenkinsimage: lachlanevenson/k8s-kubectl:v1.10.12imagePullPolicy: IfNotPresentname: kubectlresources: limits:cpu: 100mmemory: 500Mi requests:cpu: 100mmemory: 500MisecurityContext: privileged: false procMount: DefaultterminationMessagePath: /dev/termination-log
[JIRA] (JENKINS-57116) Version 1.15.1 does not create pods
Title: Message Title
Josh Chandler commented on JENKINS-57116
Re: Version 1.15.1 does not create pods
I experienced this problem with 1.15.2; a rollback to 1.14.9 does fix the issue. My log output regarding the issue at hand is exactly the same as Martin Reinhardt. The plugin will try to create a pod, fail on that error, fail to delete the pod (as it never existed in the first place), and tries all of that over again. A log recorder on org.csanchez.jenkins.plugins.kubernetes provided no more logs than watching Jenkins' own output. Versions, pod definition, and pipeline below. Not sure if this is what you're looking for exactly Carlos Sanchez - will be happy to provide more as you require. Jenkins version: 2.162 Kubernetes Version: v1.12.6-gke.10 GKE OS Version: Container-Optimized OS (latest as of 2019-04-29) Pod template:
$ kubectl get pods --export -o yaml jnlp-buildpod-cgpfm
apiVersion: v1
kind: Pod
metadata:
creationTimestamp: null
labels:
jenkins: slave
name: jnlp-buildpod-cgpfm
selfLink: /api/v1/namespaces/ci/pods/jnlp-buildpod-cgpfm
spec:
containers:
- args:
- cat
command:
- /bin/sh
- -c
env:
- name: JENKINS_SECRET
value: [redacted]
- name: JENKINS_AGENT_NAME
value: jnlp-buildpod-cgpfm
- name: JENKINS_NAME
value: jnlp-buildpod-cgpfm
- name: JENKINS_URL
value: http://ops-jenkins.ci.svc.cluster.local:8080/
- name: HOME
value: /home/jenkins
image: centos:7.6.1810
imagePullPolicy: IfNotPresent
name: cmdtools-centos
resources: {}
securityContext:
privileged: false
procMount: Default
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
tty: true
volumeMounts:
- mountPath: /var/run/docker.sock
name: volume-0
- mountPath: /home/jenkins
name: workspace-volume
- mountPath: /var/run/secrets/kubernetes.io/serviceaccount
name: ops-jenkins-token-2dszv
readOnly: true
workingDir: /home/jenkins
- args:
- cat
command:
- /bin/sh
- -c
env:
- name: JENKINS_SECRET
value: [redacted]
- name: JENKINS_AGENT_NAME
value: jnlp-buildpod-cgpfm
- name: JENKINS_NAME
value: jnlp-buildpod-cgpfm
- name: JENKINS_URL
value: http://ops-jenkins.ci.svc.cluster.local:8080/
- name: HOME
value: /home/jenkins
image: alpine:3.8
imagePullPolicy: IfNotPresent
name: cmdtools
resources:
limits:
cpu: 100m
memory: 100Mi
requests:
cpu: 100m
memory: 100Mi
securityContext:
privileged: false
procMount: Default
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
tty: true
volumeMounts:
- mountPath: /var/run/docker.sock
name: volume-0
- mountPath: /home/jenkins
name: workspace-volume
- mountPath: /var/run/secrets/kubernetes.io/serviceaccount
name: ops-jenkins-token-2dszv
readOnly: true
workingDir: /home/jenkins
- args:
- cat
command:
- /bin/sh
- -c
env:
- name: JENKINS_SECRET
value: [redacted]
- name: JENKINS_AGENT_NAME
value: jnlp-buildpod-cgpfm
- name: JENKINS_NAME
value: jnlp-buildpod-cgpfm
- name: JENKINS_URL
value: http://ops-jenkins.ci.svc.cluster.local:8080/
- name: HOME
value: /home/jenkins
image: lachlanevenson/k8s-kubectl:v1.10.12
imagePullPolicy: IfNotPresent
name: kubectl
[JIRA] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Josh Chandler commented on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens The word "generic" doesn't even occur on this page until you get to the comments: https://wiki.jenkins-ci.org/display/JENKINS/Github+Plugin I take issue with the sentiment that "nobody uses [the generic APIs]" because, in fact, the plugin documentation explicitly states that it does, in that it is able to trigger webhooks. If that is not the case, the plugin needs to be deprecated for end-user consumption and the documentation changed. There is nothing on the github-plugin page to indicate that an installable plugin is just an abstraction that I shouldn't be using for the purpose stated by the documentation. This functionality was guaranteed up until workflow. Kirill did not protest the use of the plugin in the way I have specified, leading me to believe this was expected behavior until now. If that was not the case, I would love to know why no one said anything to the contrary for seven months until you jumped on this thread. The very fact that of 19 watchers of this issue, that no one but you knew about this, is pretty incredible. In fact, if you ask google "jenkins github push trigger": guess what comes up as the very first result?:"Starting from this time" does not magically reconcile the fact that this bug was filed under completely different auspices seven months ago. If I am totally incorrect and this is the direction that the authors are taking with respect to their plugins, there is still a bug in that the documentation for the github-plugin needs to be changed to tell us we shouldn't be using it this way, and to point us to the appropriate plugins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Josh Chandler updated an issue Jenkins / JENKINS-35132 Pipeline: GitHub webhook received but nothing happens Change By: Josh Chandler Attachment: screenshot-2.png 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-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title
Josh Chandler edited a comment on JENKINS-35132
Re: Pipeline: GitHub webhook received but nothing happens
I have a bit of a problem with this resolution. In short: I disagree entirely this is not a part of the github-plugin, with evidence from the code. Two things:1) It is most certainly from this plugin. The logs I captured indicate it came from this file:https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.javaThe log I posted to Kirill Merkushev indicates it came from this line:https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java#L68Particularly on line 71 (for reference: https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java#L71), the commentary indicates it will kick a build at this point. This is the behavior I wished to occur which did not happen.2) The github-plugin page at (https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Plugin) indicates this is a primary objective of the plugin itself on the landing page:{ { quote} Trigger a job when you push to the repository by groking HTTP POSTs from post-receive hook and optionally auto-managing the hook setup.Report build status result back to github as Commit Status (documented on SO) {quote } } This is exactly what I was trying to do; and this is exactly not what is happening on my server.If this is, after this body of evidence, somehow _not_ related to this plugin, can you explain to us where we can collect the information required to find the right place to comment, and perhaps point us to this place?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title
Josh Chandler commented on JENKINS-35132
Re: Pipeline: GitHub webhook received but nothing happens
I have a bit of a problem with this resolution. In short: I disagree entirely this is not a part of the github-plugin, with evidence from the code. Two things: 1) It is most certainly from this plugin. The logs I captured indicate it came from this file: https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java The log I posted to Kirill Merkushev indicates it came from this line: https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java#L68 Particularly on line 71 (for reference: https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java#L71), the commentary indicates it will kick a build at this point. This is the behavior I wished to occur which did not happen. 2) The github-plugin page at (https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Plugin) indicates this is a primary objective of the plugin itself on the landing page: {{Trigger a job when you push to the repository by groking HTTP POSTs from post-receive hook and optionally auto-managing the hook setup. Report build status result back to github as Commit Status (documented on SO)}} This is exactly what I was trying to do; and this is exactly not what is happening on my server. If this is, after this body of evidence, somehow not related to this plugin, can you explain to us where we can collect the information required to find the right place to comment, and perhaps point us to this place?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] [github-plugin] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Josh Chandler commented on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens I believe I have, yes - I am implementing the full pipeline as in the script I originally posted, and then hitting "Build Now". I was going to install webhooks to finish out the project when I encountered the issue. The pipeline itself runs without a hitch. I am using this code to do this: stage 'Checkout Code' git credentialsId: 'my-credential-id', poll: false, url: 'https://github.com/my-org/my-repository.git' Setting poll: true makes no difference - I attempted a build just now with the flag set to true: the build was successful to the end, but the logs still read "Polling has not run yet." Is there some different incantation I should be using during the 'Checkout Code' phase that will accomplish this? Am I supposed to run an individual phase somehow instead of the entire pipeline? Is there some way I can force git-scm to initialize? 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-plugin] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Josh Chandler commented on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens I remember seeing in the plugin code where polling could possibly be run, but it simply never reaches that block. Thinking these workflow job type objects don't fit the inheritance hierarchy expected to kick off a build, so the code after the hook is received never fires. 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-plugin] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Josh Chandler updated an issue Jenkins / JENKINS-35132 Pipeline: GitHub webhook received but nothing happens Change By: Josh Chandler Attachment: github-polling-log.png 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-plugin] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Josh Chandler commented on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens 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-plugin] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Josh Chandler commented on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens Thanks for your response! I have attached a partially-redacted view of the config for the first job that gave me this issue. Particularly, I have redacted my organization name (by request of my superiors). Suffice it to say that when I do manually kick this off, it is able to reach git to pull code without an issue. The hook was installed successfully and I do receive it on my Jenkins. Here is the config for this job: "workflow-job@2.1"> false "github@1.19.1"> https://github.com/org/toy-box.git/ "org.jenkinsci.plugins.workflow.cps.CpsFlowDefinition" plugin="workflow-cps@2.2">// Define all required variables. Most will be disseminated to the environment. def projectName='toy-box' def tagName = "1.1-" + new Date().format('MMdd') + '.' + env.BUILD_NUMBER def imageName = "[REDACTED]" def clusterToken="[REDACTED]" def slack = [channel: '[REDACTED]', teamDomain: '[REDACTED]', token: '[REDACTED]'] def logPath = "/var/jenkins_home/jobs/${env.JOB_NAME}/builds/${env.BUILD_NUMBER}/log" def deploymentResponders = "Could you please have a look?" node { try { stage 'Checkout Code' git credentialsId: '[REDACTED]', poll: false, url: 'https://github.com/org/toy-box.git' stage 'Build Project' def npmLocation = tool name: 'node_5.10.0', type: 'jenkins.plugins.nodejs.tools.NodeJSInstallation' sh "${npmLocation}/bin/npm install" stage 'Automated Test' echo 'No tests defined for this project.' stage 'Build Docker Image' sh "docker-build.sh --image ${imageName}" slackSend channel: slack.channel, color: 'good', message: "Docker image build success for build #${env.BUILD_NUMBER} of ${projectName}!", teamDomain: slack.teamDomain, token: slack.token stage 'QA Deployment' echo 'QA Deploy is being skipped at the moment. Please contact an administrator for more details.' stage 'QA Testing Begins' echo 'QA Test is being skipped at the moment. Please contact an administrator for more details.' stage 'QA Testing Passed' echo 'QA Test is being skipped at the moment. Please contact an administrator for more details.' stage 'Production Deployment' slackSend channel: slack.channel, color: 'good', message: "Awaiting deployment approval for build #${env.BUILD_NUMBER} of ${projectName}. " + deploymentResponders, teamDomain: slack.teamDomain, token: slack.token input message: 'Ready to roll out?', ok: 'Go!' sh "cloud-deployment.sh --image ${imageName} --deployment ${projectName} --token ${clusterToken}" slackSend channel: slack.channel, color: 'good', message: "Production deploy success for build #${env.BUILD_NUMBER} of ${projectName}!", teamDomain: slack.teamDomain, token: slack.token } catch (org.jenkinsci.plugins.workflow.steps.FlowInterruptedException fx) { slackSend channel: slack.channel, color: 'red', message: "Build ${projectName}:#${env.BUILD_NUMBER} aborted.", teamDomain: slack.teamDomain, token: slack.token } catch
[JIRA] [github-plugin] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title
Josh Chandler updated an issue
Jenkins / JENKINS-35132
Pipeline: GitHub webhook received but nothing happens
Change By:
Josh Chandler
I apologize if this is something known that I've overlooked.I've created a small pipeline project in Jenkins to manage Github pushes against some of my enabled repositories. These jobs were brand new, typed as Pipeline jobs (not multibranch - I haven't got the buy-in from my developers to add Jenkinsfiles yet). I have Jenkins configured to automatically create webhooks against these projects, which works perfectly. I am also able to manually run jobs, whereupon I can pull the code and the pipeline builds out as intended.The problem lies in Jenkins kicking off the build when the POST is received. For all of these repositories, watching the Jenkins logs, I see this:{ { noformat} May 25, 2016 4:09:45 PM org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber onEventINFO: Received POST for https://github.com/[org]/[repo] {noformat } } But afterwards, nothing happens: no build starts, no exceptions are triggered, nothing. I've read through the plugin and thought this might be a mismatched class type for the job, but I am not a pro at Java, much less Jenkins plugin syntax.Am I missing something here? Is there lacking support for this version?VERY much appreciate any help anyone can provide. I've been tearing my hair out about this for a few days.
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
[JIRA] [github-plugin] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title
Josh Chandler created an issue
Jenkins / JENKINS-35132
Pipeline: GitHub webhook received but nothing happens
Issue Type:
Bug
Assignee:
Kirill Merkushev
Components:
github-plugin
Created:
2016/May/25 4:39 PM
Environment:
Jenkins 2.3 Github Plugin 1.19.1 Git Plugin 2.4.4
Priority:
Minor
Reporter:
Josh Chandler
I apologize if this is something known that I've overlooked.
I've created a small pipeline project in Jenkins to manage Github pushes against some of my enabled repositories. These jobs were brand new, typed as Pipeline jobs (not multibranch - I haven't got the buy-in from my developers to add Jenkinsfiles yet). I have Jenkins configured to automatically create webhooks against these projects, which works perfectly. I am also able to manually run jobs, whereupon I can pull the code and the pipeline builds out as intended.
The problem lies in Jenkins kicking off the build when the POST is received. For all of these repositories, watching the Jenkins logs, I see this:
{{May 25, 2016 4:09:45 PM org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber onEvent INFO: Received POST for https://github.com/[org]/[repo]}}
But afterwards, nothing happens: no build
