-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Create build.sh #23180
Create build.sh #23180
Conversation
retest windows_release_unit32_prtest please |
# Note that while ~ usually refers to $HOME, in the case where $HOME is unset, | ||
# it looks up the current user's home dir, which is what we want. | ||
# https://www.gnu.org/software/bash/manual/html_node/Tilde-Expansion.html | ||
export HOME=$(cd ~ && pwd) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't we need this anymore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
think this is required for mac builds.
test mac please |
Well, that mac test exploded pretty hard:
The reason it's not needed anymore is because that code is duplicated in |
test mac please |
Mac test "passed": CI has been broken for a while, it's just that no tests ran, and so jenkins freaks out and reports a failure (even though everything executed normally). (this was happening before this PR, so this PR should be okay to merge. We should probably fix that, though...) |
The interface is a rough parallel to
build.cmd
. Note that this script will be compatible with the repo API going forward, and so minor changes may happen to make sure it's exactly aligned with the repo toolset - also note that this PR doesn't try to be 100% compatible with the repo API, it's just a starting point, because the linux story is painful right now and I can't stand it anymore 😛.The biggest win here, in my opinion, is less telling users to run things in
./build/scripts
, which IMO should be an internal-only directory (nobody should ever run scripts directly from there).(
obtain_dotnet.sh
is in there, but hey, one step at a time 😊)ping @jaredpar