Archive

Posts Tagged ‘hudson’

Clean Code Developer

February 8th, 2010 bfluri No comments

ccd_bannerIt took me quite some time to replace the Clean Code Developer bracelet; it took me way more time than the usual three weeks because 1) the principles are fundamental and 2) I didn’t have much opportunity to use them all. But, now, I think it’s definitely time to switch from the yellow to the green bracelet. The principles and practices of the green bracelet are:

  1. Open closed principle: open for extension, closed for change (Object-Oriented Software Construction by Bertrand Meyer)
  2. Tell don’t ask
  3. Law of Demeter: Personally, I don’t think this principle can be used steadily nowadays. If you work with frameworks, you seldom have a chance to follow this principle striclty.
  4. Continuous Integration: I recommend the article of Martin Fowler for a very good introduction and the Podcast fom se-radio.net For our project, we use Hudson as the continuous integration server.
  5. Static code analysis
  6. Inversion of Control Container
  7. Pass knowledge
  8. Measure bugs

Seminar on Software Testing

September 10th, 2009 bfluri No comments

Today I gave a seminar on software testing for PhD students and professionals at the University of Zurich. During the seminar, I used the uDoo demo application to show how to use Maven and Hudson for automated testing.

Let Subversion trigger your Hudson build job

September 3rd, 2009 bfluri 3 comments

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.