git hooks and how they work
/usr/bin/curl -u user:secret http://localhost:8080/hudson/job/MyJob/build?token=secondsecret
If I force a build, hudson updates the code, but here’s what I don’t understand, the hooks in that repo DON’t have the .sample after them like they do locally, and the post-receive in the hudson repo doesn’t have that line of code above. What’s going on here and how are hooks integrated into the whole git process? Do I need to be changing this hook on the remote repo? I would have thought it was enough to do it locally and push so anyone fetching from that repo get the new hooks. I can’t understand how another user’s repo would have different hooks.
2 Solutions collect form web for “git hooks and how they work”
You basically have two options:
- Place the
post-receivehook on the server and let the server run curl.
- Place a
post-commithook on your local repo and let your local box run curl.
As your build job will probably fetch the code to build from the repo on the server, only option 1. makes sense. In case 2., the build job would probably have to fetch the code from your local box, and that is probably not what you want.
You cannot place hooks onto the server using
git push. You (or someone with the appropriate permissions) needs to do that by manually logging into server and modifying the hook script files locally.
Hooks are not shared through the repository. You need to install the hook at the remote side.