Using Continuous Integration

The Continuous Integration area lets developers check information on backend and frontend builds.

From Continuous Integration in the Developer area, you can find information about your backend and frontend builds such as branch, date, build status, and short commit hash. Additionally, you can access the related build logs and commit diff.

For further information on continuous integration, see Continuous integration.

View build logs

To view the build logs, follow these steps:

From the Studio home page or from the left menu, go to Developer > Continuous Integration.
Hold your pointer over the build of which you want to see the build logs.
Click the Build log icon: the Build log dialog opens.
In the Build log dialog do the following:
- To view backend extensions build logs, expand the sections in the Backend tab. You can also download the logs by clicking Download raw log.
- To view frontend build logs, click either Frontend staging or Frontend production: Humio build log opens.
  To access the frontend build logs from these links, you must use Humio as your log management system for your Netlify sites. If you change the log setup on Netlify, you cannot access frontend build logs from the Studio.

View commit diff

To view the commit diff, follow these steps:

From the Studio home page or from the left menu, go to Developer > Continuous Integration.
Click the Short commit hash of the build for which you want to view the commit diff: a new tab with the GitHub commit diff page opens in your browser.

If you are using a custom continuous integration for your custom Git repository, you cannot view the commit diff.

Build status

The Backend status column displays the status of the backend extensions build and can have the following values:

Success: the backend extensions build was successful. You can deploy it from the Deployment area. Otherwise, if you set the deploy parameter to true when uploading the build from a custom CI, the build is automatically deployed to the staging environment.
Failure: the backend extensions build failed.

The Frontend staging status column displays the status of the build for the frontend staging site and can have the following values:

Pending: Netlify has not started the build for the frontend staging site.
Processing: Netlify is processing the build for the frontend staging site.
Success: the build for the frontend staging site was successful. You can deploy it from the Deployment area. Otherwise, if you set the deploy parameter to true when uploading the build from a custom CI, the build is automatically deployed to the staging environment.
Canceled: Netlify skipped the build for the frontend staging site either because the build has been in the Pending status for more than 24 hours or the backend extensions build failed.
Failure: the build for the frontend staging site failed.

The Frontend production status column displays the status of the build for the frontend production site and can have the following values:

Pending: Netlify has not started the build for the frontend production site.
Processing: Netlify is processing the build for the frontend production site.
Success: the build for the frontend production site was successful. You can deploy it from the Deployment area.
Canceled: Netlify skipped the build for the frontend production site either because the build has been in the Pending status for more than 24 hours or the backend extensions build failed.
Failure: the build for the frontend production site failed.

Do not deploy directly from Netlify. It causes issues with your deployment due to inconsistencies between frontend and backend extensions build versions.

To avoid build version mismatch, deactivate auto publishing on Netlify by locking deploys.

The Studio updates the build statuses asynchronously about every five minutes. Therefore, there might be a mismatch between the statuses displayed in the Studio and Netlify.