Posts Tagged ‘ Hudson ’

CI Gossip: Is Hudson asking Jenkins out again?

After the recent divorce of Hudson and Jenkins following the tragical death of Hudson’s mother Sun and a long battle over trademark rights, Hudson seems to have come to senses and is planning to hand over the code to Eclipse. I’ve seen Jenkins’ father Kohsuke in Hamburg earlier this week where he presented some stats [ READ MORE ]

Distributed CI: How it could work

I think distributed CI is the logical next step in the evolution of Continuous Integration by getting rid of the manual step of running a private build on the developer machine before committing to the master repository. Here is how I imagine this might work. Managers, developers and customers (or all stakeholders if you will) [ READ MORE ]

Hudson is dead. Long live Jenkins.

Watch out. There is a new butler in town. Today the Hudson community representatives in the negotiations with Oracle announced that Hudson is likely to be renamed to Jenkins. The proposal also suggests to move all infrastructure off Oracle’s servers. This will be decided in the next few days, after Oracle’s expected proposal later this [ READ MORE ]

Why distributed CI is the logical next step

It has become a best practice to run a private build on the developer machine before committing a change to the central source repository to minimize broken CI builds. Despite being a sensible measure to improve the development process this practice has always bugged me, because it is an extra manual step. In my opinion [ READ MORE ]

Continuous Integration (CI) – the missing pieces

Continuous Integration (CI) has been around for a while now, and is part of most decent development environments these days. It is certainly mature enough to not give you an excuse any more for not using it. Yet there are a few features that I haven’t found in any CI tool I have used so [ READ MORE ]

Deployments should be non-events

The problem with “traditional” release management I say “traditional” release management for the lack of a better categorisation. What I mean by that is having separate phases (and teams) for development, system test, user acceptance test (UAT) and finally production. The problem is that it just takes too long after the developer commits his code [ READ MORE ]

Java Build Server

Update [15.05.2010]: I finally had a chance to try out SecureCI, which is pretty much exactly what I described in this post. The guys from Coveros did a great job, so I suggest after reading this post you head over to their website, download SecureCI and give it a go. Thanks John for pointing this [ READ MORE ]

Follow

Get every new post delivered to your Inbox.

Join 119 other followers