Add testing of the release manifest file usage in the build script

Open
#5,338 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
40/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
shell

Research direction

Start at build.sh line 36, where the VMR build script accepts the SB release manifest file, and review the linked source-build issue 5337 for the regression context. Add automated coverage for this manifest-file usage and verify that the test catches the reported class of build-script issue.

Written by the indexing model from the issue text.

Description

area-testing

The VMR's build script takes the SB release manifest file as input: https://github.com/dotnet/dotnet/blob/92464d46540df2a24d896d56bf825a6ec67aa47f/build.sh#L36

There should be automated testing of this logic of the build script in order to avoid issues like https://github.com/dotnet/source-build/issues/5337.

Dominant language
No language data
Stars
287
Forks
146
Avg merge
1d 22h
Merged PRs (30d)
10

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/source-build

All issues in dotnet/source-build

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.