This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Created Pipeline Configuration File #512
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Description
Currently, we have several different configuration files across our repos that control the behavior of various pipelines. This pull request merges all of those configuration files into one, enabling you to define every configurable aspect of behavior on any pipeline running against this repository, for existing and future pipeline features.
The file is defined in JSON and allows line comments, but no block comments. The root of the JSON object includes a named object for each pipeline. Every pipeline supports at least two child objects,
pipeline-branchandenvironment. Support for other child objects, such asdependenciesorconfiguration, depend on the pipeline.The existence of this
pipeline.jsoncfile will cause these standalone config files to be completely ignored. Once this centralized config file is merged into all relevant branches, support for all standalone config files will be removed.See auto-buildkite-pipelines pull request 99 for more information.
API Changes
None.
Documentation Additions
None.