Print create-dmg output for better logs
#296
Closed
Conversation
This file contains 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
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.
Related to #135
Proposed Changes
I propose to print the
create-dmgoutput when running the tool vianpm run make:dmg-arm64to give the callers more information on what the automation is doing.If
create-dmgnotified callers about the--skip-jenkinsside effect (maybe one day it will create-dmg/create-dmg#182) and we had logs in CI, then I wouldn't have been wondering why there was no background in the DMG generated in CI.Testing Instructions
See CI for the logs behavior
Before
After
Currently waiting for CI...
Pre-merge Checklist