> For the complete documentation index, see [llms.txt](https://docs.servoy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.servoy.com/reference/servoy-cloud/cloud-control-center/application-overview/applications/pipelines/jobs/packages/build-markers.md).

# Build markers

## Overview

Build markers are indicators of warnings and errors that occur during the process of generating a build package. They serve as essential pointers to issues that may affect the quality and functionality of the build package.

Understanding and addressing build markers is crucial for maintaining the quality and reliability of your build packages. They provide valuable insights into potential issues that require attention during the development and deployment process.

{% hint style="warning" %}
Please note build markers are only generated by Build and Deploy or Build jobs.
{% endhint %}

## Build marker types

Build markers refer to the following:

### Warnings

Warnings typically indicate issues that don't prevent the build from completing but should be addressed.

### Errors

Unlike warnings, errors signify critical issues that can prevent the build from succeeding.

## How to access

You can easily access the Build Markers Overview from various locations within the Cloud Control Center:

### Warning or Error Badges

Throughout the Cloud Control Center, you'll encounter warning and error badges associated with build jobs. Clicking on these badges will lead you to the Build Markers Overview, where you can explore the details of warnings and errors.

### Package Details Quality Reports

In the Package Details page, there is a dedicated Quality Reports tab. Clicking on this tab allows you to access the Build Markers Overview. Here, you can get a comprehensive view of the build markers associated with your package.

\\


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.servoy.com/reference/servoy-cloud/cloud-control-center/application-overview/applications/pipelines/jobs/packages/build-markers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.