> 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/configuration.md).

# Configuration

## Overview

In the package details view, the "Configuration" section outlines any configuration changes made to the [job configuration](/reference/servoy-cloud/cloud-control-center/application-overview/applications/pipelines/jobs/job-configuration.md) compared to the previous build. This list is read-only and primarily serves as a reference for tracking configuration changes between consecutive builds.

If there have been no changes in the configuration since the previous build, this section also provides a simple way to access the current job's configuration settings.

## How to access

You can navigate to the package configuration history by navigating to Package Details and choosing the Configuration tab. Also, you can access this view by using the number of configuration changes clickable stat available in the Package Builds History.\\


---

# 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/configuration.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.