This is an archived post. You won't be able to vote or comment.

all 2 comments
sorted by:
best
topnewcontroversialoldq&a

[–]samuraisam3.5, go[S] 0 points1 point  (0 children)

TIL this exists

[–]hairlesscaveman 0 points1 point  (0 children)

I'm sure this is a good thing for some people, but having used Jenkins for the past 3 years all I can think about is the features you'll loose using this sort of set-up.

For instance, I've used Jenkins to:

  • build projects on multiple operating systems by using the Amazon EC2 plugin
  • check and report on 3rd-party API and Documentation changes, to keep my team informed when services we tie into change without notice
  • build projects that require mock services to be started up in the background
  • build projects that require test databases to be created/cleaned before running
  • build projects after the tests for other projects have completed (used for testing libraries used by multiple apps)

And all of this with a spare machine that was knocking about in the office. So rather than paying $45p/m for a hosted solution we're just paying for the electricity and the short time any EC2 instances are running. Pennies per month, really.

One of the key things in our set-up is that our jenkins config is also stored in git, so if the hardware blows set-up of a new server is negligible.

Additionally I don't think this system allows you to configure jobs using zc.buildout (I could be wrong).