Skip to content

Enable build.sh for non source build scenarios #18358

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

Merged
merged 1 commit into from
Jan 24, 2024
Merged

Conversation

ViktorHofer
Copy link
Member

  1. Define argument consistently between build.ps1 and buils.sh
  2. Add a Directory.Build.rsp file to consistently disable the new msbuild terminal logger as it doesn't work well with orchestrated builds.
  3. Make the default non source build and add the "--source-only" switch.
  4. Update the YML to pass the new switch in.

This unblocks dotnet/source-build#3682 & dotnet/source-build#3823

@ViktorHofer ViktorHofer requested a review from mmitche January 24, 2024 14:33
@ViktorHofer ViktorHofer self-assigned this Jan 24, 2024
@ViktorHofer ViktorHofer requested a review from a team as a code owner January 24, 2024 14:33
1. Define argument consistently between build.ps1 and buils.sh
2. Add a Directory.Build.rsp file to consistently disable the
   new msbuild terminal logger as it doesn't work well with orchestrated
   builds.
3. Make the default non source build and add the "--source-only" switch.
4. Update the YML to pass the new switch in.
@ViktorHofer ViktorHofer force-pushed the BuildShNonSourceBuild branch from 3a86816 to da88fc0 Compare January 24, 2024 14:36
Copy link
Member

@mmitche mmitche left a comment

Choose a reason for hiding this comment

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

I think it looks good. Logic in the new build.sh looks solid. May want to have @mthalman or @MichaelSimons give that a once over too.

Comment on lines +39 to +40
echo " --excludeCIBinarylog Don't output binary log (short: -nobl)"
echo " --prepareMachine Prepare machine for CI run, clean up processes after build"
Copy link
Member

Choose a reason for hiding this comment

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

For consistency, shouldn't these two use kebab-casing?

Copy link
Member Author

@ViktorHofer ViktorHofer Jan 24, 2024

Choose a reason for hiding this comment

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

In theory yes, but Arcade already exposes them differently and we want to eventually just use Arcade's build script: https://github.com/dotnet/arcade/blob/8853b56b0f1a9f223563e5879d3f01f409c6515a/eng/common/build.sh#L41-L42

As those are part of eng/common/build.ps1 and build.sh, they are already exposed in every .NET core stack repository. I would rather stay consistent with those and live with the local difference here.

@ViktorHofer
Copy link
Member Author

Merging to unblock @akoeplinger's CI work and @directhex's short-stack work. I'm happy to react to additional feedback post-merge via a follow-up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants