Comments on: Django continuous integration with Hudson and Nose

By: Daniel Watkins

Daniel Watkins — Tue, 06 Sep 2011 11:59:00 +0000

–cover-inclusive

By: Christoph Neuroth

Christoph Neuroth — Mon, 20 Dec 2010 13:12:00 +0000

Hey, greate writeup! I have one problem with the cobertura plugin in a python project with nosetests: It seems to ignore files which are not tested at all, so I have 100% coverage on classes, files and conditionals (which, unfortunately, is just not ture ;)). Do you have any ideas what could be causing this?

By: James English

James English — Fri, 08 Oct 2010 02:45:39 +0000

I answered my own question. I had to go into the hudson settings and set “shell executable” to “bash” for some reason it wasn’t using the bash shell

By: James English

James English — Fri, 08 Oct 2010 00:40:17 +0000

I wonder if you could help me out, I am trying to get this to work but I am running into a lot of problems

So when hudson runs my build script (which is exactly the same as your except I renamed ve to trunk) I get: /var/lib/hudson/jobs/dummy/workspace/trunk/build-settings.sh: 3: source: not found

Then when it tries to run: pip install -E ./trunk -r requirements.pip

I get: IOError: [Errno 2] No such file or directory: 'requirements.pip'

Then I get some more errors, but those are the first 2 so I figured they probably impact the rest of the errors.

Some help is greatly appreciated, I can't figure out why source won't work in the shell script. I've gone to the $WORKSPACE directory myself and run the shell script and it has worked fine!

I even tried pasting the shell script into hudson and still got the same source not found error.

By: Tim

Tim — Thu, 18 Mar 2010 12:39:46 +0000

Really good post but:

“Assuming you have a properly constructed setup.py” – No I don’t, any pointers to what is a proper setup.py for a Django app?

By: Tobias McNulty

Tobias McNulty — Fri, 12 Mar 2010 01:19:17 +0000

As another resource, Colin, one of the guys I work with, just did a writeup of our Django/Hudson setup here at Caktus:

http://www.caktusgroup.com/blog/2010/03/08/django-and-hudson-ci-day-1/

It walks you through setting up a new Hudson installation to test a Django project – hope someone finds it useful!

By: Jacob

Jacob — Thu, 04 Mar 2010 21:30:37 +0000

Thanks!

By: Chris

Chris — Mon, 22 Feb 2010 13:20:39 +0000

Jacob,

The settings module is a regular python file that can live anywhere on your Python path. It’s documented on the “Django Web site”:http://docs.djangoproject.com/en/1.1/topics/settings/

Often times folks will have a settings module in their project folder, or if you’re building a reusable application you might have a settings file for testing inside that application.

My Hudson configuration doesn’t assume one application per Hudson project. You could run a large test suite containing many applications if you wanted.

By: jacob

jacob — Sat, 13 Feb 2010 23:31:13 +0000

Hi Chris, First, apologies, I’m a python/django noob. When you say to “create a test settings module for your application,” what exactly does this mean? If I merely parse the statement word-by-word, given my rudimentary knowledge, I take it that I should create a file with a .py extension (i.e. a module) in (one of (or all of?)) the application directories in my django project. Is that correct? If so, does it matter what the module is named? Is something somewhere supposed to refer to it? Which of my django applications should contain it? Where exactly in the dir structure of the application should it go? Does this assume one Hudson project per django app?

By: Stavros

Stavros — Wed, 30 Dec 2009 23:48:19 +0000

Word to the wise, don’t use the pypi version of django-nose, get the one from github.

By: Stavros

Stavros — Wed, 30 Dec 2009 22:35:08 +0000

Hmm, tests pass but Hudson reports a failed build. Could this be because I’m just running manage.py test?

By: Stavros

Stavros — Wed, 30 Dec 2009 19:52:11 +0000

I just tried your plugin, it is much better and I have gotten everything working fine (after setting up your plugin nose couldn’t find it, but I copied the module manually in /site-packages/). The coverage and nosetests xml files are generated fine, but for some reason Hudson reports my tests as failed, even though nosetests.xml has failures=”0″…

I’ll figure it out sooner or later, thanks for granting my request!

By: Chris

Chris — Sun, 13 Dec 2009 03:10:46 +0000

Stavros,

Give this plugin I whipped up a try, it should compliment nose's built-in coverage plugin, adding the XML output: nose-xcover

By: Chris Heisel

Chris Heisel — Thu, 10 Dec 2009 23:03:34 +0000

Stavros,

Thanks! Two thoughts, you can give the folks at Nose a ping, I sent the maintainer a pull request on BitBucket, but haven't heard back.

I'll also look and see if I can make a plugin that'd do the same thing my patch is doing.

Chris

By: Stavros

Stavros — Thu, 10 Dec 2009 21:43:44 +0000

Hello, I love your guide (and the final result), but I don’t like having to install a fork of official packages (it’s a bit hard to maintain). Do you think your changes could ever see their way upstream?

By: Chris

Chris — Mon, 23 Nov 2009 14:02:26 +0000

Joe,

Didn’t have to do much to get it to use the virtualenv.

I’m running the tests via a shell job, so all I had to do was create the virtualenv and source it.

This gist http://gist.github.com/240296 is pretty much our build command. Then we have one other build command for pylint using what you had in your tutorial.

By: Joe Heck

Joe Heck — Mon, 23 Nov 2009 01:18:39 +0000

Nice writeup! I’ve been wondering about nose & django together, but hadn’t yet found the django-nose piece.

Did you have to do much work on the system hosting Hudson to enable virtualenv? Would love to see/hear what you specific build steps look like for this setup.