Frequently Asked Questions

This is a collection of common questions we get when people are trying Codefresh for the first time.


Q. What is Codefresh?
A. Codefresh is a Continuous Integration/Delivery solution. It fetches code from your GIT repository and packages/compiles it. Then it deploys the final artifact to a target environment. This basic concept is implemented with pipelines.

Q. Is there an on-premises version of Codefresh?
A. Yes. Codefresh is offered in SAAS, Hybrid and on-premises modes. Before you consider on-premises please look at the hybrid mode first. In this mode Codefresh runs the Web UI while you only maintain the build nodes behind the firewall.

Q. Is Codefresh open-source?
A. The Web UI is not open source. All the pipeline plugins and the Codefresh Runner are open-source. We also publish several open-source components, examples and demos.

Q. How is pricing structured?
A. Pricing is per concurrent build. In practice this means how many pull requests you can process at the same time. See the pricing page for more details.

Q. Is there a pay as you go model?
A. We are always considering new pricing options. The pay as you go model has flaws as well. One of the big selling points of Codefresh is the different types of caches we employ in order to speed up builds. When a company charges for build minutes, it has no further motivation to cut down on build times. Several CI solutions offer no caching mechanisms, forcing you to download application dependencies on each build. Please contact us to discuss about pricing if this is your main blocker from adopting Codefresh.

Q. Does Codefresh offer infrastructure for running builds?
A. Yes, the cloud version of Codefresh is fully SAAS. You only need to open an account and all builds are running on our cloud. You can still use a Codefresh runner to run builds on your own infrastructure, but this is completely optional.

Q. Does Codefresh offer infrastructure for test environments?
A. Yes, each Codefresh account has access to preview environments that are powered by Docker Swarm. You can also run integration tests with Databases, Key-Value stores, message queues etc.

Q. Does Codefresh offer infrastructure for production deployments?
A. No. You need to connect your own cloud provider either in the form of VMs, or Kubernetes cluster or Docker Swarm etc.

Q. Can I deploy with Codefresh to non-Kubernetes targets?
A. Yes. Even though Codefresh has great support for Docker and Kubernetes, you can still use it to deploy plain VMs, JAR files, static websites, Wordpress instances, Database changesets etc. Here is an example with a traditional VM deployment.


Q. How is Codefresh different that another CI solution?
A. This is a long discussion. The quick answer is :

  1. Codefresh is a full CI/CD solution and not just CI.
  2. Codefresh works with all major Git platforms and Cloud providers. There is no lock-in with any particular vendor.
  3. Codefresh has several unique features such as a distributed docker layer cache, an automounted shared volume, a private Docker registry and a private Helm repository.
  4. Specifically for Kubernetes/Helm, Codefresh has a Kubernetes dashboard, a Helm dashboard, a Helm charts browser and a Helm environment board.
  5. The Docker registry integrations and all cluster integrations are automatically available to all pipelines. You don’t need docker login commands or kubectl commands to setup a Kube context inside your pipeline.
  6. Codefresh covers the full software lifecycle. You can see a release on the cluster dashboard, click on it, go to the docker image, click on it and go the build that created it, all from a single interface. Codefresh is batteries-included CI/CD.

Q. How is Codefresh different than Jenkins?
A. Codefresh is a superset of Jenkins. Jenkins is only CI. You need to write custom scripts or use another tool such as Ansible to deploy with Jenkins. See the comparison matrix and the detailed blog post. There is also a comparison with Jenkins X.

Q. How is Codefresh different than my custom deployment scripts in bash/Ansible/Chef/Puppet/Python?
A. These scripts are custom made, complex to maintain and difficult to read. One of the reasons that developers and operators have difficulties in communication is the in-house nature of deployment scripts. Codefresh allows you to create standard declarative pipelines where each step is a reusable Docker image.

Integration features

Q. Can Codefresh run a build on each push/commit?
A. Yes, this is one of the most basic functions of a CI system. See our extensive git support. You can also run builds in a cron-like manner or even from Docker push events from several popular Docker registries.

Q. Can Codefresh build pull requests?
A. Yes, this is one of the most basic functions of a CI system. See our extensive git support and built-in variables.

Q. Can Codefresh build applications in programming language X?
A. Yes, Codefresh is agnostic in this manner. The only requirement is that you have a Docker image with the compiler/framework/libraries of your programming language. See some examples for Java, Go, Node.js, Ruby, Php, Python, C++, C#.

Q. Can Codefresh build applications which are not Dockerized?
A. Yes. Even though Codefresh is especially powerful with containers, you can still use it for traditional applications which are not deployed in containers. Here is an example with a plain Go executable and another with a C executable.

Q. Can I run tests in my pipelines?
A. Codefresh supports all kinds of tests such as unit tests and integration tests as well as test reports.

Q. Does Codefresh support parallelism?
A. Yes, Codefresh supports both parallel steps (parallelism within a pipeline) as well as parallel pipelines.

Q. Does Codefresh support preview environments for pull requests?
A. Yes, although notice that these are powered by Docker swarm. If you want preview environments in a Kubernetes namespace you need to connect your own cluster.

Q. Can I checkout code from non-git sources?
A. Yes, you can checkout code from other source control systems.

Q. Does Codefresh support git submodules?
A. Yes, there is a git submodule plugin.

Q. Does Codefresh support git monorepos?
A. Yes, there is built-in support for monorepos.

Q. Does Codefresh support pipeline-as-code?
A. Yes, all pipelines can be stored in a git repository (the same one as the application code or a different one). You can also create pipelines programmatically with our CLI.

Q. Does Codefresh support secrets?
A. For basic usage, feel free to use the shared configuration facility. For production grade security we suggest a dedicated solution such as Hashicorp Vault. We offer a vault plugin for this purpose.

Q. Can I call external service X in a pipeline?
A. Yes, everything that has an API or CLI can be called in a Codefresh pipeline (Artifactory/S3/Slack/SonarQube/Twistlock/Codecov etc)

Deployment features

Q. Can I deploy to different environments (dev/staging/prod)?
A. Yes, you can even deploy in parallel to several environments. If you also use Helm you get a nice graphical dashboard.

Q. Can I pause a pipeline and wait for approval before deploying to production?
A. Yes, there is a built-in approval step.

Q. Can I deploy to non-Kubernetes targets?
A. Yes, you can deploy to a VM, an FTP site, an application server or even a behind-the-firewall Nomad cluster. You can deploy to anything that has an API or CLI.

Q. Does Codefresh support infrastructure as code?
A. Yes, there is nothing special to it. See the Terraform and Pulumi examples.

Q. Can I connect my own Docker registry?
A. Yes, you can connect your own external registry as long as Codefresh has network access to it.

Q. My Kubernetes cluster has automatic scaling/monitoring/logging. Will Codefresh have issues with it?
A. Codefresh is using the standard Kubernetes API available to all compliant Kubernetes distributions. After a deployment is finished, Codefresh does not tamper with the cluster in any way.

Q. Do you support deployment to Kubernetes clusters on Azure, Amazon, etc?
A. Yes, we do! If your master node is publicly accessible you can access it as a custom provider, just follow the cluster connection instructions. In addition, we have native integration with GKE, Azure, Amazon, and Digital Ocean. Native Integration with more cloud providers is coming soon.

Q. Can I run Codefresh pipelines on my Kubernetes cluster?
You can but you don’t need to. The SAAS version of Codefresh is fully managed and pipelines are running on the cloud. You can run Codefresh pipelines on your own cluster using the Codefresh Runner in Hybrid mode. This is normally only needed if you want to access services behind your firewall. If you simply want to deploy to a Kubernetes cluster, the SAAS version of Codefresh is enough.

User interface

Q. What toolkit does the Codefresh UI use?
A. We use Angular JS.

Q. Can I use Codefresh without the graphical dashboards?
A. Yes, all Codefresh functionality is available via our API and CLI.

Q. What are the browser requirements for the Codefresh UI? A. We officially support the latest version of the Chrome browser. Any browser released in the last 2 years should work without any major issues. The following browser versions are NOT supported:

Browser Version Date released
Chrome < 51 May 2016
Firefox < 54 Jun 2017
Edge < 14 Aug 2016
Safari < 10 Sep 2016

Enterprise support

Q. Does Codefresh support SSO?
A. Yes, we support several popular SSO providers.

Q. Does Codefresh support access control?
A. Yes, we support both UI and ABAC on pipelines, projects and clusters.

Q. Does Codefresh support auditing?
A. Yes, audit logs are built-in.

Q. Is Codefresh security certified?
A. We are currently SOC2 compliant and are working to get other certifications as well.

Q. Do you offer professional services to help us migrate to containers/Kubernetes?
A. Yes, we do.