System Settings
Admin
BP’s System Settings #
The System Settings page in BuildPiper provides centralized control over a wide range of platform-level configurations required to manage security, integrations, and operational behavior — enabling organisations to standardize workflows, enforce policies, and ensure scalable, secure, and efficient pipeline execution across environments.
Login & SSO #
Enables users to securely log in to BP using their Google account credentials via OAuth2 authentication.
Allows enterprise users to authenticate using Active Directory (LDAP) for centralized identity and access management.
Provides SSO login through GitHub accounts, simplifying access for development teams.
Enables authentication using GitLab credentials for streamlined access to BP.
Allows users to sign in using Bitbucket accounts via secure OAuth2 authentication.
Supports login through Microsoft accounts or Azure AD for enterprise-grade authentication.
Optimisation Settings #
Specifies the default time interval (in seconds) after which the pipeline execution view automatically refreshes.
Enables support for Job Template v3, allowing use of dynamic and custom job definitions within the platform.
Provides stage approval scheduling to control when approvals can be actioned within a pipeline.
CI #
Defines a custom tagging pattern to be applied during CI build executions for consistent artifact versioning.
Enables support for CI versioning to track and manage build versions across the continuous integration pipeline.
Clean-up #
When enabled, automatically cleans data from the database on a set frequency interval to prevent storage bloat.
When enabled, cleans logs from the host machine on a fixed interval, ensuring efficient disk utilization.
Removes intermediate Docker images from the host machine to free up disk space after build executions.
White Listing #
Defines whitelisted IPs for Git webhooks to control which sources can trigger pipeline events.
Specifies the domain to be allowed for a specific Git provider, controlling which Git sources can interact with BP.
CD #
During canary deployment, each new deployment in Kubernetes must have a unique name. A suffix is appended to ensure uniqueness across rollouts.
When enabled, loads build tags from the database for use during deployment selection.
Enables support for CD versioning to track deployment versions and maintain controlled release histories.
Mis #
Provides environment hierarchy configurations to control how artifacts are promoted across environments.
Sets the timeout limit for Build & Deploy tasks to prevent long-running jobs from blocking the pipeline.
Sets the manual build and deploy flag for the environment master, giving teams explicit control over deployments.
Configures the pipeline task timeout duration to manage how long a task can wait before being marked as failed.
Configures CloudWatch information to push custom metrics from BP into AWS CloudWatch for observability.
Enables BuildPiper platform versioning to track and manage version information across the platform.
Configures daily user status reports to be sent to administrators for platform activity monitoring.
Ticketing System #
Configures basic Jira integration and workflow mapping to connect BP pipeline events with Jira issues.
Maps Jira transition names to BP pipeline stages for automated issue status updates during deployments.
Defines the Jira pattern used to detect and extract Jira issue IDs from commit messages or branch names.
Enables proxy support for Jira connections, allowing BP to communicate with Jira through a configured proxy server.
Configures basic ServiceNow (SNOW) integration and workflow to link BP deployment events with SNOW change records.
Multi-Arch Support #
Configures a remote SSH endpoint for Docker Buildx to enable multi-architecture image builds across remote nodes.
Enables support for adding multiple target architectures to BP build pipelines for cross-platform image generation.
Feature Flags #
Sets the list of queues to be used for build, promote, and deploy operations, enabling targeted task routing.
Enables transactional rollback support to revert pipeline or deployment changes atomically on failure.
Allows specific applications to be pinned for quick access or locked at a specific version within the platform.
💡 Important: After applying changes in System Settings, the user must log out and log back in for the updates to synchronize and take effect.
📘 BuildPiper Documentation · System Settings
Last updated: March 2026