In our previous announcement for the removal of the Codefresh Docker registry, we presented a timeline of the migration phases along with the actions expected from our customers. One of the milestones in the migration process is the introduction of our new Image API along with several enhancements on the pipeline build step. We believe that these features deserve a dedicated explanation of why they are useful on their own (regardless of the registry removal).

Today we are announcing the removal of the built-in Docker registry that comes built-in with all Codefresh accounts. The registry will become read-only on April 15, 2020 and we’re aiming to remove it completely May 1, 2020.

Long before Dockerfiles, Java developers worked with single deployment units (WARs, JARs, EARs, etc.). As you likely know by now, it is best practice to work in micro-services, deploying a small number of deployment units per JVM. Instead of one giant, monolithic application, you build your application such that each service can run on its own. This is where Docker comes in!

One of the central ideas behind the Codefresh GUI is giving as much information as possible to both developers and operators regarding the status of a deployment. Just because a pipeline has finished successfully does not always mean that the respective environment is healthy.

Like in 2018, now that 2019 is gone, it is time to look back and see all the major Codefresh features that were added over the past year. The highlight of the year was, of course, the world’s first live debugger for CI/CD pipelines, a feature that makes us really proud since it changes completely the way you create and analyze CI/CD pipelines.

At Codefresh, we know that any CI/CD solution must be attractive to both developers and operators (SREs). One of the major advantages of Codefresh is the graphical user interface that includes dashboards for Kubernetes and Helm deployments. These graphical dashboards are very useful to developers who are just getting started with deployments and pipelines.

Open source components have become a basic building block in today’s software development process. It’s no surprise that 60%-80% of the codebase in 92% of modern applications is open source — they provide us with tried-and-true code that allows us to save time and focus on creating the secret sauce that will make our products the next great tech innovation.

If you have selected Gitlab as your git provider, you may automatically think about selecting GitlabCI as your CI/CD solution as well. Using the same vendor for source control and CI/CD might seem natural, but is not always the best combination. In fact, choosing a “good-enough” option just because it is part of the same solution is unwise in the long run if it doesn’t cover your needs.

We as a company, and I as a human have been enormous beneficiaries of open source. I remember as a kid, my brothers setup a Renegade BBS so other people could call our computer. A few years later I built my first server running on NetBSD. And of course, we all used the internet. Open source has powered so much of my life. I still remember my first accepted open-source contribution, it was an incredibly minor fix for an HTML5 Quake game, but wow was I proud.

Close eyed observers may have noticed that we’ve been testing out a new free tier and today we’re ready to announce it to the world. From today, on, Codefresh has free unlimited builds. Yes, you read that right. We’re launching unlimited builds/workflows on our free plan. The free plan comes with everything you need to build a great CI/CD pipeline.