We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It can be a maven download failure or something related to Kaniko/S2I.
E.g. this happened right now to me:
time="2018-12-11T15:34:49Z" level=info msg="step failed with error: cannot instantiate binary: builds.build.openshift.io \"camel-k-kotlin-1\" already exists" context=kotlin logger=builder phase=40 step=publisher/s2i
It's usually a temporary error but it blocks the platform because there's currently no recovery mechanism.
We should wait with an exponential backoff and retry.
The text was updated successfully, but these errors were encountered:
Same policy should be applied to integrations requiring a full image.
Sorry, something went wrong.
IntegrationContext builds sometimes fail apache#279
c5af21e
68a3a77
da17160
831d151
lburgazzoli
No branches or pull requests
It can be a maven download failure or something related to Kaniko/S2I.
E.g. this happened right now to me:
It's usually a temporary error but it blocks the platform because there's currently no recovery mechanism.
We should wait with an exponential backoff and retry.
The text was updated successfully, but these errors were encountered: