The fifth annual DevOps and Jenkins Community Survey is here and it brings some very interesting insights into the usage of technology environments, adoption of practices and DevOps maturity levels within organizations. Let’s take a closer look at the most interesting highlights.
Is DevOps already old news? And if this really is the case, is GitOps simply the latest iteration of this concept or is there more to it? We caught up with Tracy Miranda, Director of Open Source Community for CloudBees at JAX London 2018 to talk about the concept behind GitOps, how Jenkins X fits into this new approach and more.
Are you ready for the next stage of development? JAX London speaker Tracy Miranda explains how GitOps is ready to save the day in the event of complete system failure.
Now that the Jenkins & Java 10 Online Hackathon is behind us, Tracy Miranda looks back at the event and shares the things she learned about Jenkins and Java 10.
Jenkins requires Java 8 as there are some known compatibility issues with higher Java versions. However, the time has come to do some serious Java 10 investigation and have some fun while at it! Why not participate in the Jenkins & Java 10 online hackathon?
We’re back with a new programming pub quiz! This week, we’re testing your knowledge about Jenkins. Do you know everything there is to know about this provider for automated software solutions?
New project alert! Jenkins X is built on Jenkins’ shoulders but its focus lies on automating CI/CD for the cloud using Jenkins, as well as other open source tools including Kubernetes and Git. Let’s take a look under its hood.
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.