jq isn't installed on the container running a scan. It isn't needed, so
this wraps the statement in an `if binary exists`. block
This also enables slack notifications on failure.
https://buildkite.com/elastic/kibana-sonarqube/builds/224
## Summary
These were used for testing the migration from the kibana-buildkite
infra to the elastic-wide buildkite infra. Now we're done with most of
the migration, we can clean these up.
## Summary
This PR moves the definitions of the following pipelines from
`catalog-info.yaml` to `.buildkite/pipeline-resource-definitions`:
- `buildkite-pipeline-kibana-emergency-release` ->
`.buildkite/pipeline-resource-definitions/kibana-serverless-emergency-release.yml`
- `kibana-tests-pipeline` ->
`.buildkite/pipeline-resource-definitions/kibana-serverless-quality-gates.yml`
More details in the original PR #186833, which is split into the
creation of the new pipeline (#187251) and moving existing pipelines
from catalog-info.yaml to .buildkite/pipeline-resource-definitions (this
PR).
## Summary
This PR adds separately quality gate pipelines for the emergency release
process.
This gives us the opportunity to run a different set of checks during an
emergency release compared to a regular release.
### Details
- Add new emergency quality gates pipeline definitions in
`.buildkite/pipelines/quality-gates/emergency`. These are copies of the
regular quality gates pipeline files with the following adjustments:
- The entry point `kibana-serverless-quality-gates-emergency.yml` has an
adjusted `QG_PIPELINE_LOCATION` and comment
- The QA quality gates in `pipeline.tests-qa.yaml` is reduced to just
the CP e2e tests
- Add new pipeline
`.buildkite/pipeline-resource-definitions/kibana-serverless-quality-gates-emergency.yml`
is added that will trigger the emergency version of the quality gates.
### Other changes
In order to have things around the serverless quality gates and the
emergency release consistent, I've taken the opportunity and moved the
definitions of the following pipelines from `catalog-info.yaml` to
`.buildkite/pipeline-resource-definitions`
- `buildkite-pipeline-kibana-emergency-release` ->
`.buildkite/pipeline-resource-definitions/kibana-serverless-emergency-release.yml`
- `kibana-tests-pipeline` ->
`.buildkite/pipeline-resource-definitions/kibana-serverless-quality-gates.yml`
## Summary
Another episode of the https://github.com/elastic/kibana/pull/178136
saga. It seems I can't find a way to figure out `file` based locations,
backstage always says they don't exist. It's also apparent, that a
sourcegraph.com doesn't show any public `catalog-info.yaml`s that would
use a `type: file` - so it could be a broken approach to begin with.
## Summary
This job is to help with the kibana-buildkite -> elastic-wide buildkite
migration (https://github.com/elastic/kibana-operations/issues/15).
The idea is the following:
- this PR will create a backstage resource in `catalog-info.yaml` that
triggers the creation of a buildkite pipeline. (*)
- this pipeline will be within the `gobld` universe, using the
elastic-wide infrastructure and agent images.
- if we use this pipeline, edit, and run on a specific branch, we can
test further pipelines in the `gobld` universe, thus we can test a
pipeline's behavior before creating a resource for it, or altering the
currently existing pipelines
(*) - by creating this pipeline, it also tests the idea of having a
router file (`locations.yml`) instead of cramming every pipeline def to
`catalog-info.yaml`
## Summary
Removes resource def and pipeline for:
https://buildkite.com/elastic/kibana-serverless-release
Adds a step after deploy tag creation to trigger a GPCTL release flow
for the commit hash - this step needs to be emitted because some of its
parameters are not available at the time of uploading the original
pipeline file.
- [x] Test without firing off a release
<img width="1250" alt="Screenshot 2024-02-23 at 11 43 08"
src="f8b2fd04-8b44-4beb-949e-5f45a3573bc5">
Closes https://github.com/elastic/kibana-operations/issues/59 - see this
for the full context.
---------
Co-authored-by: Thomas Watson <w@tson.dk>
## Summary
Adds a pipeline that will trigger the promotion and QG for kibana
through qa -> staging -> production whenever the tag which [matches the
regex](https://regex101.com/r/tY52jo/1) is created.
Sibling PR [here](https://github.com/elastic/serverless-gitops/pull/661)
that defines `main/gen/gpctl/kibana/tagged-release.yaml`
The meat of the PR is the regex.
---------
Co-authored-by: Thomas Watson <w@tson.dk>
Co-authored-by: Alex Szabo <delanni.alex@gmail.com>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Adds the Kibana UI and Kibana Background Tasks services to the Backstage
configuration.
## Summary
Summarize your PR. If it involves visual changes include a screenshot or
gif.
### For maintainers
- [x] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
---------
Co-authored-by: Petr Klapka <petr.klapak@elastic.co>
Co-authored-by: Jon <jon@elastic.co>
