buildpipe-buildkite-plugin
buildpipe-buildkite-plugin copied to clipboard
:shipit: Dynamically generate Buildkite pipelines based on project changes
Currently, if a workspace step depends on a project step, the plugin will generate an incorrect pipeline. For example: ```yaml - label: build key: build branches: "master" env: BUILDPIPE_SCOPE: project...
## Overview This PR addresses what appears to be a regression of behaviour introduced in: #41 Buildkite `trigger` steps don't support a top level `env` property, but the new global/project...
Hi folks. We recently swapped our repo over to use GitHub's rebase strategy for PR merges and noted that the default diff command for buildpipe doesn't work anymore (as noted...
Hi, I couldn't figure out a way to define dependencies between steps within one project. The Buildkite native way would be to use a `key: foo` and a `depends_on: foo`...
Hey there 👋 This looks like an awesome project but I was hoping to get some clarification. You mention "Especially useful for monorepos where you want to create dependencies between...
For projects, it's possible to blacklist steps by putting them into the `skip:` block. It would be great to have the same option with whitelisting, for example with an `include:`...
a blank `env` key gets appended to the `group` keys, causing the YAML to be invalid Here is our output generated by the plugin:  from 1.5.0 to 1.8.3. Release notes Sourced from github.com/sirupsen/logrus's releases. v1.8.3 What's Changed Add instructions to use different log levels for local and syslog by @tommyblue in sirupsen/logrus#1372...
Defining a global environment variable and using it in a plugin used in a pipeline step does not work: ```yaml env: MY_FOO: bar projects: - label: myproject path: - "..."...