-
Notifications
You must be signed in to change notification settings - Fork 130
Description
I would like to request that trusted contributors, such as Elastic employees, be given permissions to retry Buildkite steps. For tests that appear to be flaky due to network or third-party service problems (example given below), retrying the individual step is more time and cost efficient.
The workaround today is to trigger the entire job through a Github /test comment .
Error: error running package system tests: could not complete test run: could not setup service: could not boot up service using Docker Compose: running Docker Compose up command failed: exit status 18: Head "https://docker.elastic.co/v2/observability-ci/database-enterprise/manifests/12.2.0.1": Get "https://docker-auth.elastic.co/auth?account=jenkins_ro&scope=repository%3Aobservability-ci%2Fdatabase-enterprise%3Apull&service=token-service": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Screenshot:
