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

Create build.sh #23180

Merged
merged 1 commit into from
Nov 16, 2017
Merged

Create build.sh #23180

merged 1 commit into from
Nov 16, 2017

Conversation

khyperia
Copy link
Contributor

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

@khyperia khyperia requested a review from a team November 15, 2017 17:00
@khyperia
Copy link
Contributor Author

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)
Copy link
Member

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?

Copy link
Member

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.

@jaredpar
Copy link
Member

test mac please

@khyperia
Copy link
Contributor Author

Well, that mac test exploded pretty hard:

16:55:26 FATAL: command execution failed
16:55:26 java.nio.channels.ClosedChannelException

The reason it's not needed anymore is because that code is duplicated in cibuild.sh, so there's no need for it to be in restore.sh.

@khyperia
Copy link
Contributor Author

test mac please

@khyperia
Copy link
Contributor Author

khyperia commented Nov 16, 2017

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...)

@khyperia khyperia merged commit 4bd448a into dotnet:post-dev15.5-contrib Nov 16, 2017
@khyperia khyperia deleted the build_sh branch November 16, 2017 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants