fix: InProcess command line option behaviors#3039
Merged
timcassell merged 1 commit intodotnet:masterfrom Mar 3, 2026
Merged
Conversation
filzrev
changed the title
Collaborator
|
Need to fix merge conflicts |
filzrev
force-pushed
the
fix-inprocess-option-behaviors
branch
from
8c1e43e to
9c5f0d9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR intended to fix
--inProcesscommand line option behaviors.Currently, when
--inProcessargument is contained as argument.ConfigParser create job based on
Job.Default. and remainingbaseConfigsetting seems silently ignored.This PR modify code to use
baseJobsettings when creating InProcess toolchain job.