Skip to content

Align more tests for elastic-package to Build Kite / "/test" in GitHub #1721

@nicpenning

Description

@nicpenning

After the tests have moved to build kite in GitHub, it is a challenge for those who do not have permissions to run /test now also cannot not see the build failure messages. This lengthens the amount of time for community members or those who cannot see the failed build error messages in a tough spot to always be asking someone with permission to see what the errors are so either party can resolve.

A recent example on an integration (elastic/integrations#8993) :
image

Some other errors that I had to glean from Elastic maintainers are:

Error: can't install the package: could not zip-install package; API status code = 500; response body = {"statusCode":500,"error":"Internal Server Error","message":"Migration function for version 7.11.0 threw an error"} [cisa_kevs] run_tests_package failed

Error: there is no owner for "packages/cisa_kevs" in ".github/CODEOWNERS"

Error: owner "elastic/integrations" defined in "packages/cisa_kevs/manifest.yml" is not in ".github/CODEOWNERS"

Each of those were found in separate /test and it would be great to have these checks locally before expending other peoples time and increasing the amount of bottlenecks to integration development.

Ideally, it would be great to have all tests completed so the chance of success in the publication of an integration in GitHub is much greater.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions