Jenkins is still one of the most widely used tools in the area of continuous delivery. Why? In this interview from DevOpsCon 2017 in Berlin, we interviewed Gianluca Arbezzano about the strengths and weaknesses of Jenkins, Docker, and the future of container technology.
As more organizations adopt Jenkins as their engine for continuous delivery (CD), broader teams with varying degrees of technical skills demand a more bespoke and succinct user interface. Say hello to Blue Ocean 1.0.
The benefits companies can derive from implementing Continuous Delivery (CD) initiatives are tangible. In this article, DevOps influencer Sunil Mavadia points out the elements that lead to a more effective Continuous Delivery solution.
To many dev teams, Jenkins is synonymous with continuous integration (CI), automating the mundane tasks of integration, test and build for projects – the very thing founder Kohsuke Kawaguchi created it for, in the underbelly of Sun and Oracle. However, as more organizations adopt Jenkins as their engine for continuous delivery (CD), broader teams with varying degrees of technical skills demand a more bespoke and succinct user interface. We talked to James Dumay, Senior Product Manager at CloudBees and lead contributor to the Jenkins Blue Ocean plugin, about the need for Blue Ocean and what to expect from it in the near future.
I learned the hard way building PaaS and SaaS frameworks, and perhaps there is no easy way, but here are some tips on how you can move beyond CI to CD by taking advantage of Jenkins Workflow.
Each Monday we take a step back and analyze what has happened in the previous week. Last week we watched Bitcoin blow all expectations and Blue Ocean reshape Jenkins’ user experience and we got excited about Go 1.7. Kotlin is once again gaining momentum and Hadoop-as-a-Service got us thinking. But that’s not all folks!
Blue Ocean is reshaping Jenkins’ user experience, modeling and presenting the process of software delivery by transpiring information which is important to development teams with as few clicks as possible without sacrificing the extensibility which is core to Jenkins.
Sacha Labourey, CEO and founder of CloudBees, explains in this JAX London keynote how Jenkins-based DevOps and Continuous Delivery approaches are transforming software delivery processes.
Continuous integration techniques are useful not only for project development, but also for software infrastructures. In this video tutorial, we find out how to improve infrastructure quality, reproducibility and speed with an infrastructure-as-code approach.
Ops, hardware, infrastructure – software is still eating its way into various worlds that were once out of its reach. Meanwhile DevOps is eating up the developer’s workplace. Perforce’s Mark Warren speaks to us about the impact of everything becoming code and how DevOps is changing responsibility, security and collaboration.
Join us at the Jenkins User Conference on Tuesday for a free pop-up JAX London networking event and an exclusive talk on the plight of working for a billion dollar company.
Jenkins creator Kohsuke Kawaguchi talks Continuous Delivery, Jenkins and why it makes all the difference being the first-mover in IT.
“A massive IT transformation is currently taking place,” says the CloudBees founder – DevOps is radically changing how we deliver software. And Jenkins is right in the middle of it.
In his session at the JAX 2015’s Continuous Delivery Day, Nigel Harniman (CloudBees) explained how to build and maintain scalable, stable and simple CD pipelines, using a Jenkins enterprise solution from CloudBees. Afterwards, he spoke to us about trends and DevOps approaches.