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.