-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ci] Click to deploy cloud #205623
base: main
Are you sure you want to change the base?
[ci] Click to deploy cloud #205623
Conversation
PR Cloud deployment started at: https://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/190 |
PR Cloud deployment started at: https://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/191 |
PR Cloud deployment started at: https://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/192 |
Cloud deployment initiated, see credentials at: https://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/192 |
db2390a
to
2ef578b
Compare
2ef578b
to
005281a
Compare
Cloud deployment initiated, see credentials at: https://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/199 |
Pinging @elastic/kibana-operations (Team:Operations) |
--message "PR Cloud deployment started at: $BUILDKITE_BUILD_URL" \ | ||
--context "cloud-deploy-job" \ | ||
--clear-previous | ||
label: Comment with job URL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks broken, but works https://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/199
💚 Build Succeeded
Metrics [docs]
History
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Summary
Similar to #195581
Adds a pipeline that builds Kibana and starts cloud deployment without going through the CI test suites (as in normal pull-request pipeline runs). It can be useful if a developer would like to save time/compute on re-building/re-testing the whole project before deploying to the cloud.
Added labels (
ci:cloud-deploy / ci:cloud-redeploy
) are required similarly to the usual CI flow.Related to: https://github.com/elastic/kibana-operations/issues/121