Add jenkins-level retry for pre-merge build in databricks runtimes [databricks] #9624
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pxLi
requested review from
jlowe,
revans2,
tgravescs,
GaryShen2008 and
NvTimLiu
as code owners
Signed-off-by: Peixin Li <[email protected]>
pxLi
force-pushed
the
more-retry-when-databricks
branch
from
2e15dec
to
d6abaa8
Compare
|
build |
pxLi
changed the title
|
NIT: we could consider separating the dep download build part to save more time. but it requires some other investigation (some discussion in #9609) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We got more and more build failures while downloading dependencies since apache repos (central&sonatype) are quite unstable recently.
For CI running internally, we have URM artifactory but for external runs (like databricks) we can only try to add more retries and pray this could help mitigate the issue (we already have maven retry args but did not help too much). Managed cache on shared CSP storage could also be an option as long-term goal
This change only touches the build step. (internal pipeline has applied the same change)