fix: support plugin-only steps in monorepo-diff watch config#173
Open
Tolsee wants to merge 2 commits into
Open
fix: support plugin-only steps in monorepo-diff watch config#173Tolsee wants to merge 2 commits into
Tolsee wants to merge 2 commits into
Conversation
Steps with only a plugins field (e.g. docker-compose build steps) were silently dropped after v1.9.0 introduced hasAction() validation. Plugins alone are a valid execution mechanism in Buildkite.
Tolsee
force-pushed
the
fix/plugin-only-step-validation
branch
from
847ba55 to
fc4e0a6
Compare
This file contains hidden or 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
Buildkite supports plugin-only steps — steps where the plugin itself provides execution (e.g. docker-compose#vX, docker#vX). These steps have no command:, commands:, or trigger: field.
Since v1.9.0 (#158), hasAction() only checks those three fields, so plugin-only steps are silently dropped with a Skipping invalid step warning and never appear in the generated pipeline.