> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/tutorials/acc/how-to-manage-build-variables.md).
# How to Manage Build Variables
Build variables let you pass environment-specific values into an application's build process — for example, a private key needed to authenticate with a private package repository. Once defined, these variables are injected as environment variables during each new build and can be accessed from within `build.sh`.
{% stepper %}
{% step %}
Go to **My Applications** and click the settings icon on the row of the application you want to configure.
{% endstep %}
{% step %}
On the application's **Settings** page, click **Build Variables** to switch to the build variables tab.
{% endstep %}
{% step %}
Click **+New Build Variable** to open the form for adding a new variable.
{% endstep %}
{% step %}
Enter a **Name** and **Value** for the variable. Optionally check **Mark as secret** to hide the value after creation, then click **Save**.
{% hint style="info" %}
Once a variable is marked as secret, its value can no longer be read after creation.
{% endhint %}
{% endstep %}
{% step %}
From the list, use the actions column to edit or delete an existing build variable.
{% endstep %}
{% endstepper %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.akinon.com/tutorials/acc/how-to-manage-build-variables.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
