Comments on: How to create a deployment pipeline using Hudson

By: Geoff Bullen

Geoff Bullen — Fri, 11 Mar 2011 04:44:42 +0000

Have a look at the Hudsn and Jenkins build pipeline plugin that supports epoymen pipelines. Both fully automated, and hose that require manual intervention.

http://www.centrumsystems.com.au/blog/?p=121

By: Dan Malcolm

Dan Malcolm — Sun, 14 Nov 2010 14:53:58 +0000

In your setup, how do you manage manual triggering of deployments (to manual testing or production environments) and did you find a way to allow users to select from a range of release candidates to deploy?

I’ve looked at ThoughtWorks’ Go, which makes all this manageable via the UI, but I’m wondering whether something similar can be set up using standard CI tools.

Thanks for the post.

By: Andrew Swan

Andrew Swan — Wed, 27 Oct 2010 03:56:45 +0000

Seems to be on Scribd at http://www.scribd.com/doc/196739/The-Deployment-Pipeline-by-Dave-Farley-2007

By: Andrew Swan

Andrew Swan — Wed, 27 Oct 2010 03:50:47 +0000

The URL http://studios.thoughtworks.com/assets/2007/5/11/The-Deployment-Pipeline-by-Dave-Farley-2007.pdf is 404. In any case, is that article superseded by the recent Continuous Deployment book from Humble and Farley (which we have)?

By: Manuel Kueblboeck

Manuel Kueblboeck — Wed, 13 Oct 2010 01:42:31 +0000

Thanks for sharing.

@Xu Wei: The later stage doesn’t rebuild the binary artefacts, but reuses them from the commit stage. However, you can still run into the case where you have more than one commit job executions finished, before the acceptance test job is run. But because the acceptance test job is most likely slower than the commit job, you probably should just run the acceptance test job once with the latest successful commit job artefacts anyway. Otherwise, if you got a constant stream of check-ins, the acceptance test job executions will fall more and more behind. This is the default behaviour in Hudson. If you need more sophisticated behaviour you should have a look at the build promotion plugin.

By: xu wei

xu wei — Mon, 16 Nov 2009 02:45:54 +0000

Hi,
first, thanks for your post. I have a question, how can I make sure the two project are builded using the same version of the project? e.g. during the first project building, someone check in new things, and then the first project finished, and triggered the deploy stage, how can we make sure the deploy stage to use the same version with the commit stage?

thanks.

By: Silviu

Silviu — Wed, 03 Dec 2008 10:07:00 +0000

Hi Simon,
Very useful post, but could you please detail the steps for setting up the two projects: [Project]_Commit and [Project]_UAT? Especially the part for aggregate downstream test results.

Thank you,
Regards, Silviu.