For the benefit of those who may come across similar issue, let me share some details of how this was fixed.
Internal Setup: ============ Jenkins instance is in cloud, from the cloud we have no direct connectivity to enterprise github server which is in a data center. And, requests from Jenkins to github was routed via proxy in cloud. Given this setup, we opted to go for AWS SNS + AWS Lambda solution. Event Flow: ========== In Github repo, SNS topic is added and the payload of Github event is sent to Lambda which subscribes to SNS topic. Lambda processes the payload and relays it to appropriate Jenkins master (multiple masters in cloud). Problem: ======= However, PUSH event that reaches the master (correctly) was not triggering the job (both freestyle and pipeline). It turned out be that github URL that reaches the master was not matching with URL set in the job config. Recall from the setup section, Jenkins' communicates with the github server via the proxy. It was this URL (pointing to the proxy) that was in the job but the event payload sent from github had different URL. So, in the Lambda, we changed the URL to match with that of the proxy before relaying to Jenkins master. Eventually, this did the trick and PUSH event was followed by poking of the job that resulted in triggering a fresh build of that job. Overall, it was good learning experience. /Ram On Sunday, June 25, 2017 at 2:32:48 PM UTC+5:30, Ramanathan Muthaiah wrote: > > Hi Lee, > > >> Is it a plain pipeline job? If so, you need to click the option to >> trigger a build on a GitHub change. >> > > Yes, the job is setup as pipeline style and that option (to trigger build > on Github change) is enabled. > > Are there any extra commands needed in the pipeline job to indicate that > it should be triggered when github event occurs, like, commit or pull > request? > > /Ram > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/21aad390-d12b-44fe-b0ee-f162fa7ab17b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
