Skip to content

Add Build Success Message in Console #2971

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

Conversation

federicobucchi
Copy link
Member

@federicobucchi federicobucchi commented Oct 9, 2020

rdar://69970428

After running swift build the final output could display a ‘success message’ (if the build is successful) and some basic infos about where the generated binaries are located.
Currently, after a successful build, it ends with exit code 0 and the output is:
[476/476] Linking swift-package

Result after changes:

Success:

Screen Shot 2020-10-16 at 7 08 27 AM

@federicobucchi
Copy link
Member Author

@swift-ci please smoke test

@abertelrud
Copy link
Contributor

Thank you for putting up this PR! I'm wondering if the message should maybe say "Build Succeeded" or "Build Failed", depending on the outcome?

@abertelrud abertelrud self-assigned this Oct 12, 2020
@federicobucchi federicobucchi force-pushed the add-build-success-message branch 3 times, most recently from fa04557 to 8aca8f9 Compare October 16, 2020 14:09
@federicobucchi
Copy link
Member Author

@swift-ci please smoke test

@federicobucchi
Copy link
Member Author

@swift-ci please smoke test

@federicobucchi federicobucchi force-pushed the add-build-success-message branch from 4d4aff4 to 401a671 Compare October 21, 2020 06:17
rdar://69970428

Add Build Failed message
@federicobucchi federicobucchi force-pushed the add-build-success-message branch from 401a671 to c0d8b6b Compare October 21, 2020 18:08
@federicobucchi
Copy link
Member Author

@swift-ci please smoke test

@federicobucchi federicobucchi merged commit abb5172 into swiftlang:main Oct 21, 2020
@federicobucchi federicobucchi deleted the add-build-success-message branch October 21, 2020 20:23
@abertelrud
Copy link
Contributor

Thanks, @federicobucchi. Given that there's some work required in the existing code to make a better message possible, I think it makes sense to merge this now and then do the rest as follow-on PRs. This turned out to be a lot more difficult to implement than anticipated.

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.

2 participants