Github WebHook Integration with Jenkins

[@stennyrajkumar9336]

Awesome, thank your help, it worked for me finally after checking out so many videos, thanks a lot!!

[@hamidoahmed9985]

the Source Code Management section is no longer available, do you have another method ?

[@crudsinfotechng8127]

Can you please clarify what exactly you mean by Source Code Management section is no longer available? Unless its some kind of an automation local script based Jenkins job, for other jobs, the source code is always put up on some Git Repo and the web-hooks are the mechanism to respond to real time changes in remote Git repository.

[@goodnessofgod108]

Thank you very much☺ It is very useful

[@canye1662]

Nice videos... got a quick question how can you tigger a specific folder in same branch with 5 different micro service in different folders, let say you update just one folder in want only that folder changes be build, how u do that with freestyle project web hook setup.

[@crudsinfotechng8127]

Hello, Not sure if I understand your requirement but this is how it works: - WebHooks payloads contain information about the specific code changes in the GitHub Repository - which branch, what code etc etc - Once Jenkins gets this hook trigger from a specific repository, Jobs in Jenkins can be connected using Post Build actions (free style project) so that they can trigger one or more jobs (in your case, if there are multiple jobs - one each for every microservice, they can all be triggered from one main job which receives the web-hook) - In Git, you have a concept of sub-modules - where-in repository within repository are allowed and you could probably explore this as well - Additionally, if your micro service is Java & maven based, maven POM also has a concept of sub-modules and you can explore this as well From a Continuous Integration concept, the recommended is to build only those repositories & branches that have code changes. Hope this helps.

[@PP-km8uh]

He is asking in repo there are multiple folders and any changes made in 1 folder so that should be trigger. But I guess he did not understand about webhook. Webhook works on repo , so if you make change in any repo the build will get triggered bro it is not working on folder it works on repo. And if you are working on micro services then for each micro service you need to create repo

[@mhiriichrak6735]

Thank's a lot it helps me !!good job