The Build Does Not Start
If the build does not start, first confirm that the plugin is installed in the repository. Then check that you finished the vendor’s pipeline setup and that the push matches its build triggers. Start the connection from the vendor’s product if you have not installed its plugin yet. See Connect a CI Vendor.Buildkite Checkout Fails
If checkout fails with'remote-entire' is not a git command, check if Add the Entire plugin to every job is off on the Entire connection in Buildkite. Open that connection and turn the setting back on. It is on by default.
The Build Finishes, but Checks Stay Pending
Compare the build’s commit with the Trail’s latest commit. A result from an earlier commit does not satisfy the current requirement. Check the overall workflow status in the vendor’s product. Individual jobs can finish while the suite remains pending. If the build has finished but the suite has not updated, you will need to report the mismatch to the vendor with the repository, commit, and build link.The Plugin Gates Do Not Block Merges
Open Settings then Gates and find the gate for your CI plugin. For both Buildkite and Depot, any failed plugin build blocks merging when Required checks is empty. Populate the field only to block on specific build types. Plugin gates are available on both repositories hosted on Entire and GitHub mirrors. The separate Checks gate is available only on GitHub mirrors and controls checks reported through GitHub.A Required Check Never Reports
Check the required name in the plugin’s gate against the build your vendor reports:- For Buildkite, use the pipeline name in
org/pipelineformat, such asacme/tests. - For Depot, use the workflow name, such as
ci, or the name of an individual job at the run level.