This Monorepo plugin will assist you in triggering pipelines, as well as run commands in your CI by watching folders in your monorepo
.
Check out this post to learn more about How to set up Continuous Integration for monorepo using Buildkite.
A monorepo is a single, version-controlled code repository that houses multiple independent projects, offering benefits such as flexibility, streamlined management, and reduced tracking of changes and dependencies across multiple repositories.
This approach allows teams to:
- Reduce overhead associated with duplicating code for microservices.
- Easily maintain and monitor the entire codebase.
Check out the example monorepo source code.
If the version number is not provided then the most recent version of the plugin will be used. Do not use version number as master
or any branch names.
It defines a list of paths or path to monitor for changes in the monorepo. It checks to see if there is a change to the subfolders specified in the path
A path or a list of paths to be watched, This part specifies which directory should be monitored. It can also be a glob pattern. For example specify path: "**/*.md"
to match all markdown files. A list of paths can be provided to trigger the desired pipeline or run command or even do a pipeline upload.
A path or a list of paths to be ignored, which can be an exact path, or a glob.
This is intended to be used in conjunction with path
, and allows omitting specific paths from being matched.
This is a sub-section that provides configuration for running commands or triggering another pipeline when changes occur in the specified path Configuration supports 2 different step types.
-
The configuration for the
trigger
step https://buildkite.com/docs/pipelines/trigger-stepExample
steps:
- label: "Triggering pipelines"
plugins:
- monorepo-diff#v1.2.0:
diff: "git diff --name-only HEAD~1"
watch:
- path: app/
config:
trigger: "app-deploy"
- path: test/bin/
config:
command: "echo Make Changes to Bin"
- Changes to the path
app/
triggers the pipelineapp-deploy
- Changes to the path
test/bin
will run the respective configuration command
app/
changes made to app/bin
will not trigger the configuration. This is because the subfolder /bin
was not specified.
Example
steps:
- label: "Triggering pipelines with plugin"
plugins:
- monorepo-diff#v1.2.0:
watch:
- path: test/.buildkite/
config: # Required [trigger step configuration]
trigger: test-pipeline # Required [trigger pipeline slug]
- path:
- app/
- app/bin/service/
config:
trigger: "data-generator"
label: ":package: Generate data"
build:
meta_data:
release-version: "1.1"
- When changes are detected in the path
test/.buildkite/
it triggers the pipelinetest-pipeline
- If the changes are made to either
app/
orapp/bin/service/
it triggers the pipelinedata-generator
This will run the script provided to determine the folder changes. Depending on your use case, you may want to determine the point where the branch occurs https://stackoverflow.com/questions/1527234/finding-a-branch-point-with-git and perform a diff against the branch point.
README.md
lib/trigger.bash
tests/trigger.bats
Default: git diff --name-only HEAD~1
diff: ./diff-against-last-successful-build.sh
#!/bin/bash
set -ueo pipefail
LAST_SUCCESSFUL_BUILD_COMMIT="$(aws s3 cp "${S3_LAST_SUCCESSFUL_BUILD_COMMIT_PATH}" - | head -n 1)"
git diff --name-only "$LAST_SUCCESSFUL_BUILD_COMMIT"
diff: ./diff-against-last-built-tag.sh
#!/bin/bash
set -ueo pipefail
LATEST_BUILT_TAG=$(git describe --tags --match foo-service-* --abbrev=0)
git diff --name-only "$LATEST_TAG"
Example
steps:
- label: "Triggering pipelines"
plugins:
- monorepo-diff#v1.2.0:
diff: "git diff --name-only HEAD~1"
watch:
- path: "bar-service/"
config:
command: "echo deploy-bar"
- path: "foo-service/"
config:
trigger: "deploy-foo-service"
This controls the pipeline interpolation on upload, and defaults to true
.
If set to false
it adds --no-interpolation
to the buildkite pipeline upload
,
to avoid trying to interpolate the commit message, which can cause failures.
A default config
to run if no paths are matched, the config
key is not required, so a default
can be written with a config
attribute or simple just a command
or trigger
.
Example
steps:
- label: "Triggering pipelines"
plugins:
- monorepo-diff#v1.2.0:
diff: "git diff --name-only HEAD~1"
watch:
- path: "bar-service/"
config:
command: "echo deploy-bar"
- path: "foo-service/"
config:
trigger: "deploy-foo-service"
- default:
config: ## <-- Optional
command: echo "Hello, world!"
The object values provided in this configuration will be appended to env
property of all steps or commands.
steps:
- label: "Triggering pipelines"
plugins:
- monorepo-diff#v1.2.0:
diff: "git diff --name-only HEAD~1"
watch:
- path: "foo-service/"
config:
trigger: "deploy-foo-service"
label: "Triggered deploy"
build:
message: "Deploying foo service"
env:
- HELLO=123
- AWS_REGION
Add log_level
property to set the log level. Supported log levels are debug
and info
. Defaults to info
.
steps:
- label: "Triggering pipelines"
plugins:
- monorepo-diff#v1.2.0:
diff: "git diff --name-only HEAD~1"
log_level: "debug" # defaults to "info"
watch:
- path: "foo-service/"
config:
trigger: "deploy-foo-service"
Currently supports a list of commands
you wish to execute after the watched
pipelines have been triggered
hooks:
- command: upload unit tests reports
- command: echo success
Default: true
By setting wait
to true
, the build will wait until the triggered pipeline builds are successful before proceeding
Example
steps:
- label: "Triggering pipelines"
plugins:
- monorepo-diff#v1.2.0:
diff: "git diff --name-only $(head -n 1 last_successful_build)"
interpolation: false
env:
- env1=env-1 # this will be appended to all env configuration
hooks:
- command: "echo $(git rev-parse HEAD) > last_successful_build"
watch:
- path:
- "ops/terraform/"
- "ops/templates/terraform/"
config:
command: "buildkite-agent pipeline upload ops/.buildkite/pipeline.yml"
label: "Upload pipeline"
# following configs are available in command. notify is not available in trigger step
notify:
- basecamp_campfire: https://basecamp-url
- github_commit_status:
context: my-custom-status
- slack: "@someuser"
if: build.state === "passed"
# soft_fail: true
soft_fail:
- exit_status: 1
- exit_status: "255"
retry:
automatic:
- limit: 2
exit_status: -1
agents:
queue: performance
artifacts:
- "logs/*"
env:
- FOO=bar
wait: true
Thanks to @chronotc and Monebag for authoring the original Buildkite Monorepo Plugin.
MIT (see LICENSE)
Please read contributing guide.