Beat Fluri's Blog » Subversion http://fluri.computerscience.ch Just for the sake of it... Sat, 10 Jul 2010 20:09:52 +0000 http://wordpress.org/?v=2.8.6 en hourly 1 ambitz http://fluri.computerscience.ch/2010/01/ambitz-3/ http://fluri.computerscience.ch/2010/01/ambitz-3/#comments Mon, 25 Jan 2010 20:34:48 +0000 bfluri http://fluri.computerscience.ch/?p=160 I posted an article about our development infrastructure on our company blog. I explain how we setup Subversion.

]]> http://fluri.computerscience.ch/2010/01/ambitz-3/feed/ 0 Let Subversion trigger your Hudson build job http://fluri.computerscience.ch/2009/09/let-subversion-trigger-your-hudson-build-job/ http://fluri.computerscience.ch/2009/09/let-subversion-trigger-your-hudson-build-job/#comments Thu, 03 Sep 2009 18:55:49 +0000 bfluri http://fluri.computerscience.ch/?p=67 The continuous integration server Hudson knows several ways to trigger a build. If you’d like Hudson to build your project when the source-base changes and you don’t want to let him poll your Subversion periodically let Subversion trigger the build upon commit. To do that, first, configure your job in Hudson (Job -> Configure -> Build Triggers) with “Trigger builds remotely (e.g., from scripts)” (”uDoo” is the job name, so replace it with your job name):

hudson_build_trigger

Second, configure a post-commit hook in your Subversion repository: In the repository directory of your Subversion-server, a directory hook exists. In this directory you may already have a file post-commit with 744 permissions. If not, a file post-commit.tmpl exists. In that case, copy the file and change the permissions:

$ cd path/to/your/repository/hook
$ cp post-commit.tmpl post-commit
$ chmod 744 post-commit

To trigger the build via Subversion, just put the following line at the end of the post-commit file.

wget -b http://HUDSON_URL/job/JOB_NAME/build?token=my_automated_build > /dev/null

That’s it.

]]> http://fluri.computerscience.ch/2009/09/let-subversion-trigger-your-hudson-build-job/feed/ 3