Monitoring pipelines

Viewing your builds and logs

All pipeline activity in Codefresh can be viewed on the Builds tab. There is one global view from the left-side menu that shows builds for all projects across your organization and a project-based view from the settings inside an individual project.

Both views has the same controls and filters..

Viewing pipeline status

Each screen contains all builds sorted from the most recent to the oldest. The first time you visit the screen there are no filters defined.

By default it shows all builds that happening in Codefresh. To narrow the list you can use the filters on the top of the screen.

Applying filters on the build view

Directly above the list you can find several filters.

At the most basic level you can choose between

• Running builds that are currently executing
• Pending builds which are queued and waiting to start
• All builds regardless of running stage (this is the default)

You can further filter the builds by choosing the various filter types that specify the build job

The available filters are:

• Repositories - any of the linked repositories
• Branches - any of the available branches
• Committers - person that made the commit that triggered the build
• Status - success, error, in-progress, pending, terminated
• Type - build, launch a test environment

Notice that all filters are multiple-choice so you can select multiple values for each filter category. At any given point you can see all the active filters on top of the screen.

You can easily remove active filters, by clicking on them and adding/removing values.

For each individual build you can see several details such as the git hash, the person that made the commit, the pipeline that was triggered as well as how much time it took. On the right side you can see the docker images that belong to this pipeline, the codefresh.yml file that was executed behind the scenes as well as the logs (explained later on).

There are also two extra options if you click the small “3-dot” menu button on the right. You can rebuild a pipeline or launch a test environment from the resulting Docker image.

Notice that is you rebuild a pipeline it will trigger with the exact settings it originally had. So if this was a manual trigger where you disabled caching or changed the notification options, the new execution will still honor those settings (even if you have changed them for later builds).

Viewing logs from an individual pipeline

If you click on any individual pipeline you will see a screen that shows the logs of each individual step.

Each section in this screen corresponds to each pipeline step. The first two steps

• Initializing Process
• Cloning main repository

are Codefresh built-in steps and will appear for most builds (you can create a pipeline that doesn’t clone a git repository by default). The rest of the step names depend on your codefresh.yml (or the default step names provided by Codefresh)

Click on each step in order to see the respective log.

You can expand each individual section by clicking on its name and copy its logs with the copy to clipboard at the top right corner of the log window.

You can also search the logs by clicking at magnifying glass icon in the log window.

Monitoring Pipelines outside the Codefresh UI

You don’t always have to be in the Codefresh UI in order to monitor the status of your builds.

Monitoring Pipelines that check Pull requests

One of the most important roles of a CI platform is to automatically update the status of a GIT Pull request with the result of the respective build.

If you have setup a GIT trigger in Codefresh then by default this happens automatically without any other configuration for all automated commits (that are coming from webhooks).

If you start a build manually then by default the git status will not be updated (i.e. the result of the pipeline will not affect the status of Pull request)

If you don’t want this behavior to happen you can enable the git status update checkbox when you launch a pipeline.

This way the pipeline status will change the build status even with manual builds.

The same behavior is also available to the Codefresh CLI. In that case use the parameter --enable-notifications to specify if manually triggering a build will also change the GIT status.

Viewing Pipeline status from text/html files

Codefresh also supports build badges that allow you to show the status of Pipeline in Text files or web pages.

See the build badges page for more information.