[Ops] Adjust serverless release settings (#179250)

## Summary
When we rolled out the pipeline settings resulting from the defaults of
the backstage-way of defining resources, we encountered a few defaults
we didn't know about.

This PR adjusts these missing values (they're not relevant for this job,
as this job is more a process starter than a branch-related build job)
and renames a used pipeline implementation to something more accurate.
This commit is contained in:
Alex Szabo 2024-03-22 14:31:30 +01:00 committed by GitHub
parent 0092bb16aa
commit d7865619c8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 10 additions and 2 deletions

View file

@ -6,7 +6,7 @@ metadata:
description: Initiate kibana serverless releases
links:
- title: Pipeline
url: https://buildkite.com/elastic/kibana-serverless-release-1
url: https://buildkite.com/elastic/kibana-serverless-release
spec:
type: buildkite-pipeline
owner: 'group:kibana-operations'
@ -22,17 +22,23 @@ spec:
SLACK_NOTIFICATIONS_CHANNEL: '#kibana-operations-alerts'
ELASTIC_SLACK_NOTIFICATIONS_ENABLED: 'false'
default_branch: main
allow_rebuilds: false
skip_intermediate_builds: false
repository: elastic/kibana
pipeline_file: .buildkite/pipelines/serverless_deployment/create_deployment_tag.yml
pipeline_file: .buildkite/pipelines/serverless_deployment/run_serverless_release_assistant.yml
provider_settings:
build_branches: false
build_pull_requests: false
publish_commit_status: false
trigger_mode: none
build_tags: false
prefix_pull_request_fork_branch_names: false
skip_pull_request_builds_for_existing_commits: false
teams:
kibana-release-operators:
access_level: MANAGE_BUILD_AND_READ
everyone:
access_level: READ_ONLY
schedules:
Weekly automated promotion to QA:
cronline: 0 6 * * 1

View file

@ -1,4 +1,6 @@
## Lists potential commits for deployment
## Creates deploy@<timestamp> tag on Kibana
## Then kicks of the deployment to QA
agents:
image: family/kibana-ubuntu-2004