Daniel Schauenberg described at QCon London how Etsy, renowned for its DevOps and Continuous Delivery practices, does 50 deploys/day. A fully automated deployment pipeline, thorough application monitoring and IRC-based collaboration are all important to achieve this rate of change while keeping risk to a minimum. Etsy has about 60 million monthly visits and 1.5 billion page views per month.
Yesterday, a developer on the Jenkins project accidentally triggered a force push on the GitHub repositories that store the Git repositories for the Jenkins codebase, wiping out several months of commits. InfoQ looks at what happened and what needs to prevent this re-occuring in the future.
Amazon's free, one-day cloud community event took place in Berlin this month. Aimed at developers, technical and business leaders, the topics of the series increasingly focus on cost effectiveness, high availability, big data and security. The summit was complemented with presentations from successful local AWS adopters.
CloudMunch launched its full-stack DevOps platform - a dashboard of pre-integrated tools for version control, build management, validation, automated testing, deployment and cloud connectors. The company claims its platform significantly simplifies deployment of applications and infrastructure.
Earlier this month, SOASTA and CloudBees released a plugin for the Jenkins continuous integration (or CI) server to run automated tests on real physical mobile devices. SOASTA released this plugin with optimizations that were developed by the creator of Jenkins, Kohsuke Kawaguchi. The plugin provides build steps for performing operations and testing mobile devices.
GitHub has open sourced Janky, their Continuous Integration server built on top of Jenkins and augmented with Hubot, a chat automation tool.
CloudBees releases Jenkins Enterprise which offers commercial support, extended long time releases up to a year and extra proprietary plugins useful to companies with large scale Jenkins installations.
At a recent Jenkins meeting, the discussion turned towards whether a reconciliation with the Hudson project was possible (after the Hudson proposal to move to Eclipse.org was released), and what would be required for that to happen. The stated requirements appear to be in conflict to moving towards either Eclipse or Apache foundations, and therefore in a reconciliation with Hudson.
With the recent proposal to move Hudson to the Eclipse Foundation, there has been speculation as to whether this will lead to a coming together of Jenkins and Hudson, or even whether the code can be relicensed under the EPL. A discussion is taking place later today on the Jenkins IRC channel to discuss whether the Jenkins community wants to be part of this or not.
Eclipse Mylyn 3.5 has just been released, bringing improvements into the task focussed view and additional bugzilla queries. But the biggest new feature is the ability to view the state of Jenkins/Hudson builds as well as drill into test failures in order to locally replicate the issue.
Whilst Jenkins 1.397 has been released, Sonatype have been pressing on with build and architectural changes to Hudson. In order to facilitate further developer interest, the Hudson codebase will be moved back to GitHub.
The first Jenkins version, 1.396, has been released with upgrade scripts that can help migrate an existing Hudson instance. Meanwhile, Oracle confirms the continuation of commercial Hudson support, and Sonatype puts their weight behind Hudson.
The votes are in, and the community voted to rename Hudson as Jenkins in a 214 to 14 split. The infrastructure is ready but not yet in use, with a migration timeline to be announced in advance to give developers time to migrate to the new organisation. Oracle will continue to support and develop Hudson at the java.net infrastructure, but for how long?
Oracle has responded to the Hudson community about how they can keep control of the Hudson name but let the community do the work. The community has responded with a vote on renaming the Hudson project to Jenkins to escape from Oracle's legal sabre-rattling.
With Oracle having applied for the trademark on the Hudson project name, and potentially putting the future of the Hudson project in future jeopardy, the Hudson developers have proposed renaming the project to Jenkins. The developers are keen to emphasise that this is a rename, not a fork, of the project since the same developers will continue to work on the renamed project.