Update example YAML to use arrays for plugins #2
Conversation
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.
Hi again Operable team 😊
(This is the same as operable/cog-bundle-buildkite-plugin#5, but I'm not sure which one you'll get to first, so here's all the info again!)
Harriet from Buildkite here 👋🏻 We’ve updated our recommended plugin syntax to use arrays instead of a map, to help ensure plugins are executed in the correct order with all agent versions.
This PR updates your readme example to be the new recommended syntax, and makes them pass the latest plugin-linter checks. I also removed the note about the unreleased Agent, as v3 has been out for a while now 😊
Let me know if you have any questions! We’d love to get the readme updated so people use the new best-practice syntax.