Closed changusmc closed 2 years ago
@changusmc first and foremost, we're so sorry for the delay on getting back to you!
The issue you mention has a lot of pointy edges. To start with:
--id
validation that makes it invalid for it to end with buildkite-plugin
unless it is a URL--id
option should not have the versioning added to itFinally, most of the issues arise from the fact that the documentation now states that you create a folder called file-counter-buildkite-plugin
so that you have a git repository with that name afterwards. That is because of agent logic that will add the buildkite-plugin
suffix if you specify a plugin as GITHUB_USER/PLUGIN_ID
. But you don't have that scenario: your folder is part of a bigger repository and you are using it as part of the repository (in the lingo: a vendored plugin), so it should not have the buildkite-plugin
suffix in the folder name. That is what is causing you to run into these (somewhat) bugs.
With all that said, there are several steps that need to be taken:
Once again, we regret it has taken us sooo long to take a look at this, we hope we will do better in the future :)
Hello,
I'm going through the example in https://buildkite.com/docs/plugins/writing and trying to create the plugin in my existing local codebase.
Below is the directory structure
In order to use this plugin, I have to add this to my pipeline
Therefore, I want to add that to my README as well.
However,
plugin-linter-buildkite-plugin
doesn't like my command when I try to validate my pluginI also tried versioning it.