Last month we announced the 3 major features we are adding to the Codefresh platform. Dashboards for DORA metrics, support for any external Continuous Integration system and a hosted GitOps service. The hosted GitOps experience (powered by Argo CD) is now available to all new Codefresh accounts (even free ones) so that simply by signing up you can start deploying applications right away to your Kubernetes cluster without having to maintain your own Argo CD installation.

Today we are pleased to announce GitLab support on CircleCI. Teams using GitLab SaaS can now build, test, and deploy on CircleCI, and access CircleCI’s most popular features like Docker layer caching and automatic test-splitting. GitLab is now the third version control system we support, in addition to GitHub and Bitbucket.

The DevOps practice of continuous integration and continuous deployment (CI/CD) improves software delivery. CI/CD platforms monitor and automate the application development process ensuring a better application, faster. CI/CD pipelines build code, run tests, and deploy a production-ready version of an application that has passed all automated checks.

Managing source code with a defined method is one vital aspect of implementing effective application development. Today, two strategies for doing this stand above the rest: trunk-based development and GitFlow. Choosing the proper method for source code control is often dependent upon several factors, such as: In this article, let’s define and compare trunk-based development and GitFlow, look at the factors that drive an organization’s decision between the two.

In software development, the name of the game is to develop reliable systems in a fast-paced manner. As development shops have evolved to increase the speed of delivery, many organizations have embraced the Agile development practices of continuous integration and continuous deployment (CI/CD). But the very nature of fast-paced development introduces challenges — particularly around the quality and the reliability of the software being developed.

Self-hosted runners allow you to host your own scalable execution environments in your private cloud or on-premises, giving you more flexibility to customize and control your CI/CD infrastructure. Teams with unique security or compute requirements can set up and start using self-hosted runners in under five minutes.

Modern enterprises understand the need to move away from developing monolithic applications to ones that make best use of the cloud to enable business acceleration at scale and speed. That means transforming development to more resilient cloud native architectures that can be readily deployed to cloud, multi-cloud, and hybrid environments. What does it mean to be cloud native?

We are introducing a change to the pull request merge checks that will make them more reliable. Specifically, we will no longer allow pull requests to be merged while a build is in progress. It was possible for a pull request to be merged while some of its builds were still in progress and for those builds to fail after the merge has completed. This created an undesirable situation if build merge checks were enabled.