Instagram's continuous deployment pipeline lets them push code faster to production, identify bad commits easily and always be release ready. Put together in an iterative manner over a period of time, the key principles behind it include a high quality test suite, quick identification of bad commits, visibility at each stage to improve buy-in from stakeholders and a working rollback plan.
Jenkins 2.0 beta is now available which includes a new Pipeline build delivery system using a DSL built on Groovy. That feature and a new user setup process aims to give users most of what the need out of the box.
XebiaLabs TestView is a test management and analytics tool, integrating the execution, data analysis and visualization of multiple functional and unit testing tools.
Google have created a Kubernetes-based open source reference implementation that automates the building of custom Google Compute Engine VM images with Jenkins and Packer. The primary goal of this work is to demonstrate how to add image creation into a build pipeline for continuous delivery, and produce artifacts that may provide increased reliability and reduced speed of VM initialisation.
CloudBees have announced they are exiting the PAAS business to focus on Enterprise Jenkins. With this new focus, they have resigned from the Java Community Process Executive Committee.
Using the Deployment Notification plugin for Jenkins developed by CloudBees and either the additional Chef Software plugin or Puppet Labs plugin, engineers can now trace every file installed by Chef or Puppet within Jenkins CI.
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.