-
Notifications
You must be signed in to change notification settings - Fork 127
[CI] Add retry to test serverless pipeline #2894
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
Conversation
test serverless |
Triggered serverless pipeline: https://buildkite.com/elastic/elastic-package-test-serverless/builds/549 |
It cannot be used Buildkite retry approach, since |
test serverless |
Triggered serverless pipeline: https://buildkite.com/elastic/elastic-package-test-serverless/builds/550 |
test serverless |
Triggered serverless pipeline: https://buildkite.com/elastic/elastic-package-test-serverless/builds/551 |
test serverless |
Triggered serverless pipeline: https://buildkite.com/elastic/elastic-package-test-serverless/builds/552 |
test serverless |
Triggered serverless pipeline: https://buildkite.com/elastic/elastic-package-test-serverless/builds/553 |
💚 Build Succeeded
History
cc @mrodm |
test serverless |
Triggered serverless pipeline: https://buildkite.com/elastic/elastic-package-test-serverless/builds/554 |
test serverless |
Triggered serverless pipeline: https://buildkite.com/elastic/elastic-package-test-serverless/builds/555 |
Closing in favor of #2901 |
Sometimes CI pipeline in charge of testing
elastic-package
with Serverless fails when creating the Serverless project:Example build: https://buildkite.com/elastic/elastic-package-test-serverless/builds/548#01993725-bd96-4312-aca7-f7bc1d972eaa/441-469
This PR adds automatic retries in the Buildkite pipeline just if the error happens when creating the Serverless project when running
elastic-package stack up
command.