The first alpha builds of Jenkins 2.0 have been released, setting the open source continuous integration project on track for a Spring release.
The project flagged up the new build’s Pipeline as Code functionality, which it said would allow users to define configuration as code, making it “easier to create simple ‘build and test’ pipelines.” More advanced pipelines can be constructed using the Groovy-based domain specific language.
The project also trumpeted the new version’s serving up of a set of recommended plugins to help new users get up and running quickly. Established users can of course define their own plugins. The interface has also had a general tidy-up.
Sticking with the needs of established users, the project said Jenkins 2.0 would be a “drop-in replacement” of the previous version, and “totally backwards compatible”.
This point was pushed last week by Sacha Labourey, CEO of Cloudbees, who told us 2.0 was on track for an H1 release. He pledged that Cloudbees would be “onboarding” the new functionality as quickly as possible into its commercialised Jenkins-powered offering. Cloudbees is the home of Jenkins project founder Kohsuke Kawaguchi.
The shift to 2.0 is long-awaited. Jenkins has arguably been around since 2004, in the guise of the Hudson project at Sun Microsystems. Following Sun’s subsuming into Oracle, the community adopted the Jenkins moniker in 2011. ®
Sponsored: Webcast: Simplify data protection on AWS