Hudson - Environment Variables | Hudson Wiki

Building a software project - hudson - Hudson Wiki

When a Hudson job executes, it sets some environment variables that you may use in your shell script, batch command, Ant script or Maven POM ¹. The following table contains a list of all of these environment variables.

Using Hudson environment variables to identify your builds | Java.net

Using Hudson environment variables to identify your builds | Java.net

So your CI server now automatically deploys your application to an integration server. You've even configured it so that you can manually deploy to the QA server using the same process. Great! But wouldn't it be nice to know exactly what build you are looking at at any point in time? Well, Hudson lets you do just that.
When Hudson runs a build, it passes in a few useful environment variables, that you can use in your build script. This is a great way to inject information about the build into your deployable application. For example, Hudson build has a unique number, which you can reference in your build scripts using something like "${BUILD_NUMBER}". This is the list of variables (taken from an obscure corner of the Hudson documentation :-)

Simple Continuous Integration / Deployment With Jenkins - Randall Degges

Simple Continuous Integration / Deployment With Jenkins - Randall Degges

Today I'm setting up a new Jenkins CI server for work, to move off our old Hudson server, so I figured this would be a good time to blog about the process, as it's so extremely helpful to us that I can't imagine ever programming without it again.

Grails and Continuous Integration: An Essential Combo | Java.net

Grails and Continuous Integration: An Essential Combo | Java.net

Grails is a fantastic framework. As well as being ultra-productive and fun to work with, it encourages good testing practices, and provides a swathe of tools to make writing unit, integration, and web tests a real pleasure. As we will see, Grails also lends itself quite well to build automation. However, Grails is not Maven. Grails has a fairly loose concept of the software development lifecycle, and is happy to let you bundle up and deploy your application as a WAR file without running all the unit and integration tests first. A Continuous Integration (CI) server can help you keep the flexibility of the Grails development process, and still ensure that your code is fully tested for each and every code change. In this article, we will take a look at how you can introduce Continuous Integration into your Grails project. More specifically, we will walk through how you can automate your Grails testing and code quality metrics with Hudson, a popular open source CI tool.

A Hudson/GitHub build process that works | ATOMIZED

⚛ A Hudson/GitHub build process that works

I’m a huge fan of Hudson, and have been since I discovered it. The biggest issue I’ve had with it is that the Git plugin just isn’t very good.
The situation has improved lately, with Andrew Bayer making significant improvements. With the features he’s added, reasonable and non-hacky workflows are no possible.
After some experimentation, this is what we’ve settled on at SimpleGeo...

Grails & Hudson Part 2: Back to basics | Lean Java Engineering

Grails & Hudson Part 2: Back to basics | Lean Java Engineering

Ok, so you’ve decided that you want to use Hudson to build your Grails projects (or have read part 1 and want to use CodeNarc too).
If you don’t know where to start, you’ve come to the right place.
The basic steps (and we’ll go into more detail on each one) are:
1. Download Hudson
2. Run Hudson
3. Download Hudson plugins
4. Configure Hudson
5. Create a Hudson job
6. Watch the trends

This post will get you started and subsequent posts in the series will add even more power to your CI process.

Grails & Hudson part 1: CodeNarc | Lean Java Engineering

Grails & Hudson part 1: CodeNarc | Lean Java Engineering

Grails has a rich plugin eco-system with over 400 hundred plugins – so it’s easy to miss something useful. If you’re serious about software craftsmanship, then using static code analysis tools should be part of your quality regime as it gives further insight into the code base (and if you insist, yes it’ll help with your Technical Debt management).
CodeNarc provides static code analysis for Groovy and the CodeNarc plugin for Grails allows you to perform this analysis with the “grails codenarc” script. Behind the scenes this uses the CodeNarc ant task and settings from grails-app/conf/Config.groovy and produces an HTML report by default.