QG Scaffold #163831
QG Scaffold #163831
Conversation
The main question is here did I get the ownership correct, is there a better group to name? From what I understand the main thing ownership enables is writing secrets to the repo's namespace in vault for buildkite.
imkarrer
added
the
release_note:skip
|
I think the ownership in a "Component" is just a backstage component entity link to the team. The vault space is opened for github repos, so I believe we need to have Probably we can add the kibana-tests pipeline here already in this PR. Depending on the way the solutions team wants to define their quality gates: |
| - label: ":pipeline::fleet::seedling: Trigger Fleet Kibana Tests for ${ENVIRONMENT}" | ||
| command: echo "replace me with Fleet specific Kibana tests" | ||
| agent: | ||
| image: "docker.elastic.co/ci-agent-images/basic-buildkite-agent:1688566364" |
There was a problem hiding this comment.
cc @juliaElastic this and the pipeline below for staging is where we may hook in the smoke pipeline you're working on. Please leave any feedback here if you see any problems.
…a into register-kibana-backstage
|
@watson, from our side this is ready to go. |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
The main question is here did I get the github team names correct for fleet and security? Are there any other groups I am missing who will have quality gates they want to see execute on every kibana release?
Rel: https://github.com/elastic/ingest-dev/issues/2201
Rel: https://elasticco.atlassian.net/browse/QX-282