Skip to content
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

WT-12554 Treat git clone failures as setup failures in Evergreen #10428

Merged
merged 11 commits into from Apr 4, 2024

Conversation

jbergler
Copy link
Contributor

@jbergler jbergler commented Mar 27, 2024

In the evergreen builds we have a number of places where git clone is invoked in the middle of a complex build step. This can result in git problems being tracked as "test failures"

This PR either:

  • factors out those commands into their own steps where possible and marks them as setup steps to allow us to better track failure reasons in our build stats; or
  • replaces them with an equivalent that doesn't require network access (eg git worktree add)

In the evergreen builds we have a number of places where `git clone` is invoked
in the middle of a complex build step. This can result in git problems being
tracked as "test failures"

This PR factors out those commands into their own steps where possible and marks
them as setup steps to allow us to better track failure reasons in our build
stats.
@jbergler jbergler requested a review from lukech March 27, 2024 20:49
test/evergreen.yml Outdated Show resolved Hide resolved
test/evergreen.yml Outdated Show resolved Hide resolved
@jbergler jbergler requested a review from lukech April 3, 2024 20:18
@jbergler jbergler marked this pull request as ready for review April 3, 2024 20:18
@@ -3065,9 +3074,8 @@ tasks:
#######################################################
# Obtain the complexity metrics for the 'previous' code
#######################################################
git clone https://github.com/wiredtiger/wiredtiger.git wiredtiger_previous
git worktree add --detach wiredtiger_previous "${github_commit}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I learnt the git worktree command today :)

Copy link
Contributor

@lukech lukech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Well done!

@jbergler jbergler added this pull request to the merge queue Apr 4, 2024
Merged via the queue into develop with commit b63ea1d Apr 4, 2024
7 checks passed
@jbergler jbergler deleted the wt-12554-run-git-clone-as-setup branch April 4, 2024 03:44
tod-johnson-mongodb pushed a commit that referenced this pull request Apr 19, 2024
)

In the evergreen builds we have a number of places where `git clone` is
invoked in the middle of a complex build step. This can result in git
problems being tracked as "test failures"

This PR either:
- factors out those commands into their own steps where possible and
marks them as setup steps to allow us to better track failure reasons in
our build stats; or
- replaces them with an equivalent that doesn't require network access
(eg `git worktree add`)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants