chore(Windows): add -DryRun
option to build.ps1 script
#545
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 adds a
DryRun
switch argument that can be passed to the Windows build.ps1 script, allowing to run it in dry-run mode.Testing done
Normal build: https://ci.jenkins.io/job/Packaging/job/docker-agent/job/PR-545/9/
Replayed build on Windows only, with
-DryRun
activated: https://ci.jenkins.io/job/Packaging/job/docker-agent/job/PR-545/8/consoleReplay diff:
Outputs
Stage "build and test" calling
./build.ps1 -DryRun test
:Stage "deploy" calling
./build.ps1 -DryRun -RemotingVersion 3186.vc3b_7249b_87eb_ -BuildNumber 1 -DisableEnvProps publish
:Note: I'm aware of tags containing a duplicated remoting+build_number in them (
3186.vc3b_7249b_87eb_-1-3186.vc3b_7249b_87eb_-1
): #546This PR is a preliminary step which helped me fixing this issue, fixed in #547.
Submitter checklist