-
Notifications
You must be signed in to change notification settings - Fork 15
Automate library publishing. #477
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
Conversation
JaCoCo Code Coverage 94.07% ✅
Generated by 🚫 Danger |
📊 Benchmark Comparison ReportSummary
No significant changes (25 benchmarks)
Regression threshold: ±10% with non-overlapping confidence intervals Generated by 🚫 Danger |
| return result | ||
| } | ||
|
|
||
| if (project.hasProperty('releaseBuild')) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also maintain ability to publish to public maven (since it's an open source library). It would be ideal to support two different profiles of publishing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
.buildscript/upload_archives.sh
Outdated
| #!/bin/bash | ||
|
|
||
| # Use -PmavenCentralRelease for Maven Central | ||
| GRADLE_ARGS="-PartifactoryRelease" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if this script should accept an argument for the type of release
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Automate library publishing:
mastermasterVERSIONfile changesVERSIONfile to allow GitHub Workflow monitoring