Codefresh Update: Better multi-service repo support, badges, and YAML logging

Codefresh Update: Better multi-service repo support, badges, and YAML logging

2 min read

Have some suggests for Codefresh? Leave a comment!

Setting build contexts for multi-service repos

When developing at scale teams often choose to put each service in its own repo. But when working with microservices, and especially with a Docker composition it’s also common to see several services in a single repo. We now fully support this development model by allowing you to define multiple services in a single repo, each with it’s own build context.

The build context is defined using a relative path to your repository’s root directory. So if you have a Node.js service setup at /app/nodejs/ you can set your build context to /app/nodejs/ and all build and test scripts will execute relative to that path.


To get started adding multiple services from a single repo, click the +  button and set a new build context.

Add additional Docker services

View build success right from your repo

When approving pull requests it’s incredibly important to know that code passes unit and integration tests. That’s why we’re introducing Codefresh build badges so you can see if code is passing builds right from your repo. Check it out:

Codefresh build status

You can read the documentation here. Feel free to leave comments below with links to your open source repos to showoff your badges!

Build YAML exposed in builds

Logs have always been available for every build but you can now view the YAML file used to direct each build, whether it was auto generated or manually set. To view, goto builds and click the yaml-icon icon. Find build YAML file

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

Build your GitOps skills and credibility today with a GitOps Certification.

Get GitOps Certified

Ready to Get Started?
  • safer deployments
  • More frequent deployments
  • resilient deployments