days
0
-38
-3
hours
0
-5
minutes
-5
-7
seconds
0
-9
search

#continuous integration

Second part of our CI/CD expert check

Continuous Delivery Expert Check 2020 – Kubernetes and the future of CI/CD (Part 2)

Continuous delivery and continuous integration are far more than simply buzzwords or emerging trends. Automation is advancing inexorably, especially on the DevOps scene. But how will CI/CD develop in the coming year? And why is delivering software continuously so important? For our big Continuous Delivery Expert Check 2020, we asked seven respected experts in the field about these and other topics. In the second and last part of our expert check, you can learn how Kubernetes and containers have changed software delivery, what CI/CD tools our experts recommend, and what they believe the future holds.

First part of our CI/CD expert check

Continuous Delivery Expert Check 2020 – CI/CD, security & rolling deployment (Part 1)

Continuous delivery and continuous integration are far more than simply buzzwords or emerging trends. Automation is advancing inexorably, especially on the DevOps scene. But how will CI/CD develop in the coming year? And why is delivering software continuously so important? For our big Continuous Delivery Expert Check 2020, we asked seven respected experts in the field about these and other topics. In the first part of our expert check, see what best practices can help ensure security and what type of deployment our experts prefer – blue/green deployment or rolling deployment?

How all the pieces fit together

Building a strong CI/CD pipeline

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.

Modernize your processes

4 steps to implement a CI/CD pipeline

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!

Recorded in front of a live JAXconf Audience

Pre-Tested Commits in Jenkins – Kohsuke Kawaguchi at JAXconf

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

Bringing code to the Cloud and back again

Task-focused Continuous Integration

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.

  • 1
  • 2