9.9. Builds and Automation
This section outlines the configuration options available for managing automated builds within Red Hat Quay. These settings control how Dockerfile builds are triggered, processed, and stored, and how build logs are managed and accessed.
You can use these fields to:
- Enable or disable automated builds from source repositories.
- Configure the behavior and resource management of the build manager.
- Control access to and retention of build logs for auditing or debugging purposes.
These options help you streamline your CI/CD pipeline, enforce build policies, and retain visibility into your build history across the registry.
Additional resources
9.9.1. Dockerfile build triggers fields 링크 복사링크가 클립보드에 복사되었습니다!
This section describes the configuration fields used to enable and manage automated builds in Red Hat Quay from Dockerfiles and source code repositories. These fields allow you to define build behavior, enable or disable support for GitHub, GitLab, and Bitbucket triggers, and provide OAuth credentials and endpoints for each SCM provider.
| Field | Type | Description |
|---|---|---|
| FEATURE_BUILD_SUPPORT | Boolean |
Whether to support Dockerfile build. |
| SUCCESSIVE_TRIGGER_FAILURE_DISABLE_THRESHOLD | Number |
If not set to |
| SUCCESSIVE_TRIGGER_INTERNAL_ERROR_DISABLE_THRESHOLD | Number |
If not set to |
Dockerfile build support example YAML
# ...
FEATURE_BUILD_SUPPORT: true
SUCCESSIVE_TRIGGER_FAILURE_DISABLE_THRESHOLD: 100
SUCCESSIVE_TRIGGER_INTERNAL_ERROR_DISABLE_THRESHOLD: 5
# ...
| Field | Type | Description |
|---|---|---|
| FEATURE_GITHUB_BUILD | Boolean |
Whether to support GitHub build triggers. |
| GITHUB_TRIGGER_CONFIG | Object | Configuration for using GitHub Enterprise for build triggers. |
|
.GITHUB_ENDPOINT | String |
The endpoint for GitHub Enterprise. |
| .API_ENDPOINT | String |
The endpoint of the GitHub Enterprise API to use. Must be overridden for |
|
.CLIENT_ID | String |
The registered client ID for this Red Hat Quay instance; this cannot be shared with |
|
.CLIENT_SECRET | String | The registered client secret for this Red Hat Quay instance. |
Github build triggers example YAML
# ...
FEATURE_GITHUB_BUILD: true
GITHUB_TRIGGER_CONFIG:
GITHUB_ENDPOINT: https://github.com/
API_ENDPOINT: https://api.github.com/
CLIENT_ID: your-client-id
CLIENT_SECRET: your-client-secret
# ...
| Field | Type | Description |
|---|---|---|
| FEATURE_BITBUCKET_BUILD | Boolean |
Whether to support Bitbucket build triggers. |
| BITBUCKET_TRIGGER_CONFIG | Object | Configuration for using BitBucket for build triggers. |
|
.CONSUMER_KEY | String | The registered consumer key (client ID) for this Red Hat Quay instance. |
|
.CONSUMER_SECRET | String | The registered consumer secret (client secret) for this Red Hat Quay instance. |
Bitbucket build triggers example YAML
# ...
FEATURE_BITBUCKET_BUILD: true
BITBUCKET_TRIGGER_CONFIG:
CONSUMER_KEY: <your_consumer_key>
CONSUMER_SECRET: <your-consumer-secret>
# ...
| Field | Type | Description |
|---|---|---|
| FEATURE_GITLAB_BUILD | Boolean |
Whether to support GitLab build triggers. |
| GITLAB_TRIGGER_CONFIG | Object | Configuration for using Gitlab for build triggers. |
|
.GITLAB_ENDPOINT | String | The endpoint at which Gitlab Enterprise is running. |
|
.CLIENT_ID | String | The registered client ID for this Red Hat Quay instance. |
|
.CLIENT_SECRET | String | The registered client secret for this Red Hat Quay instance. |
GitLab build triggers example YAML
# ...
FEATURE_GITLAB_BUILD: true
GITLAB_TRIGGER_CONFIG:
GITLAB_ENDPOINT: https://gitlab.example.com/
CLIENT_ID: <your_gitlab_client_id>
CLIENT_SECRET: <your_gitlab_client_secret>
# ...