Bickel Blog

CloudBees announced today that our Platform as a Service for Java , RUN@cloud, will be running on VMWare's ubiquitous vSphere and the emerging OpenStack platform. This is great news for Java developers and people deploying Java applications. Platform as a Service is certainly sweeping the development community like app servers did a decade ago. It brings a new level of savings, efficiency and agility. No need to worry about all the deployment and provisioning details. Just develop and go! PaaS is part of a stack, though. And customers will have many requirements about the stack they run on. This announcement opens up all sorts of flexible and affordable options for running your Java applications: - Run on Amazon. - Run on your own servers that have vSphere already. - Run on your own servers on the new, low cost, open source OpenStack IaaS. This addresses many customer's desire to get off the VMWare high cost virtualization wagon. It moves the virtualization up to the J...

As I wrote a month ago , there was a lot of emotion around the Jenkins - Hudson split, but the reality is they are two separate projects. The purpose of this blog is to look at what has transpired over the past month and a half and how it is obvious why Hudson users should upgrade to Jenkins. It was triggered by a company wanting input on whether they should go down the Hudson or Jenkins route. They had talked with Jason at Sonatype to get the Hudson version and they wanted to talk with KK and others for the Jenkins side. I put together a bunch of data (mostly collected from others) and thought I would share it. Here are the reasons why Jenkins will win: Jenkins Developers If you liked Hudson, you will like Jenkins. The developers who wrote 99% of the core are now writing Jenkins. This includes Kohsuke Kawaguchi, the original creator of Hudson. And of course it is built on the same base. We think this will lead to more stability, better bug crushing and more new features faster....

Thought I would post some of the Twitter messages about upgrading to Jenkins or new Jenkins Plugins over the past 5 days. Nice list... atonewell Lee Upgraded our build server from @hudsonci to @jenkinsci today. Painless. redspot357 Andreas Simon mission accomplished: #continuousintegration with @jenkinsci #maven #cuke4duke #selenium-webdriver _godin_ Evgeny Mandrikov Gentoo Ebuild for #JenkinsCi 1.398 available : http://code.google.com/p/godin-gentoo-repository/wiki/Jenkins tomhe Tomas Hellberg Migrated all Autoliv #HudsonCI production servers to #JenkinsCI. Went smoothly as expected. msonnabaum msonnabaum Setting up automated testing for #drush using @jenkinsci. Lewisham Chris Lewis This is what a bad couple of days looks like #jenkinsci http://skit.ch/bg6a orrc Christopher Android Plugin for #jenkinsci now lets you control hardware properties (e.g. RAM size, keyboard present/not) http://bit.ly/gjtrQ8 jenkins_release Jenkins releases RAD Builder Plugin 1.1.3 #jenkinsci mitchblevins M...

I just got news that Ken Olsen has passed away. It makes me sad. It makes me recall his influences on my life. In 1981 I was getting my MBA at night while working as an engineer at Leeds & Northrup designing local area networks built to the joint Xerox/Intel/DEC Ethernet Specification . I had my sights set on becoming a product manager, and figured I needed to understand why people buy. I started looking for a sales job and ended up going to Digital Equipment Corporation . I went for a couple of reasons. First, they had a policy where they did not pay sales people commissions so they would act in the best interests of the customer. That felt right to me. Second, the people were amazing. Third, they were growing very fast and there was a lot of opportunity. When I joined revenues were about $1 B, and when I left 11 years later they were over $13 B. Pretty fast growth for back in those days... Once I got inside, it was amazing to see the culture. It was a combination of p...

There has been a lot of emotion and effort over the past several months regarding the split of Hudson and Jenkins. I obviously have ties to Kohsuke, and tend to side with him on the Jenkins movement. Certainly the general public reaction has been strongly in favor of Jenkins, which is really encouraging. Stepping back a bit, I think this winds up being a good thing since it has created a sense of competition in the market and made room for two approaches. Certainly the Jenkins community has a renewed sense of energy from the old Hudson community. The ideas that have emerged over the past couple of months seem to be getting a lot of momentum - improved quality, improved communications, open governance, improved documentation and roadmaps and so forth. It is clear the community is much larger than just Kohsuke. It is also clear that very large users are moving to Jenkins and have confidence in this community. On the old Hudson side, Oracle and Sonatype have stepped in with a new ap...

Well, my first month of producing energy. 290 KWH. Close to 10 KWH per day. About enough to light 100 light bulbs for an hour... You can read more on the solar panel installation on my earlier blog.

The Hudson community is currently voting on whether to rename the project. Since it is on Github, my assumption is that if there is a name change, then it will simply be made to the project. That would then mean that Oracle would then fork from that code and I am guessing bring it onto it's own servers. There have been other instances where a project renamed itself. I recall with EJBoss was told by Sun it was breaking the EJB trademark and had to rename itself. Probably one of the biggest favors Sun ever did for JBoss. However, I am not aware of a project renaming itself like this and a fork happening back to the previous name. I wonder if this is a first?