Building a stronger CI/CD pipeline isn’t easy. It requires plenty of time, tools, and the contributions of many. However, when done correctly, it has potential returns that will are worth the time involved. Benefits including automated code testing, faster software iterations, satisfied customers, a competitive edge, and more productive teams, just to name a few.
Continuous integration and continuous delivery (CI/CD) is a shortened feedback cycle that helps companies ship more software while minimizing mistakes, increasing developer productivity, and improving customer sentiment. Get four important steps for implementing a CI/CD pipeline the correct way. It can be a rigorous process, but it is worth it!
Which tools are best when you’re looking to integrate code into a shared repository several times a day? Nitish Tiwari has the lowdown on the software you need to keep your continuous integration game strong.
Are your continuous integration and delivery efforts for documentation floundering? It might serve you well to read up on how OpenStack treat documents like code and implement a strategy to successfully merge and publish.
JAXenter talks to Jeff Sussna about the evolution of DevOps, vast and deep lean practices, and what companies could be doing to up their continuous delivery game.
First Hudson release under Eclipse Foundation brings plug-in manager and reduced footprint, but is it enough?
Devops means many things to many people.
Kohsuke Kawaguchi, creator of Jenkins and architect at CloudBees, discusses how to use Jenkins to efficiently shift more workload from your laptops and computers to servers. By using “pre-tested commits” you can make changes safely so that your changes don’t block others, run tests asynchronously, and avoid compounding errors intrinsic to large projects with numerous developers contributing to the repository. Advances in distributed version control systems (such as Git) made it possible to test every commit separately before it hits the team’s main branch. This helps you keep the main branch more stable, and lets you get more values out of the CI server. In this session, Kohsuke look at the details of this technique, and how to make it work with your projects. It covers
Keeping an eye on the brightest sparks entering Google’s Summer of Code is no easy task, and we managed to miss the really cool Jenkins JaCoCo plugin from Ognjen Bubalo. Check it out
It’s been a arduous but well worthwhile task as Eclipse Hudson takes shape in M3
The CI server and binary repository join forces to launch a solution for the Jenkins community
This talk from Mik Kersten of Tasktop Technologies will explore connecting enterprise Java stacks with cloud deployment via a task-focused continuous integration loop. The SCM, code review, and Agile ALM technologies, based on the Eclipse Mylyn ALM interoperability platform, will be used to demonstrate how to achieve this new level of connectivity and automation between the team and the application. The talk will conclude with a roadmap of how we can apply these new lessons to define the next decade of enterprise Java productivity.
Just a good dose of spring cleaning from the Hudson team, after last month’s mammoth launch.
Jenkins (formerly known as Hudson) is a continuous integration server that facilitates the automation in software development. In this talk, Hudson/Jenkins founder Kohsuke Kawaguchi discusses what’s new in the project, as well as various techniques to get more out of your Jenkins server, such as distributed build techniques, some key plugins, and larger scale choreography that spans across many jobs for sophisticated automation.
