-
Notifications
You must be signed in to change notification settings - Fork 3
bom update #254
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
bom update #254
Conversation
|
Going down weird rabbit holes. In all cases, the tests are dying with exit codes which makes it hard to debug |
|
At this point, we've identified the tests needed to be disabled to get the builds working with |
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## develop #254 +/- ##
=============================================
+ Coverage 69.71% 70.18% +0.46%
- Complexity 1038 1052 +14
=============================================
Files 47 47
Lines 6070 6070
Branches 799 799
=============================================
+ Hits 4232 4260 +28
+ Misses 1482 1472 -10
+ Partials 356 338 -18
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Kudos, SonarCloud Quality Gate passed!
|
|
Locally confirmed, the same tests needed to be disabled to get the builds working with |
Description
Investigating the issue with #253
Splitting the difference on the bom update
Review Instructions
n/a except that regular (non-cron) builds should include the 1.15.0-alpha.5 bom and other parts of dockstore
Issue
n/a but split out from #253
Two follow-up issues:
Security
If there are any concerns that require extra attention from the security team, highlight them here.
Please make sure that you've checked the following before submitting your pull request. Thanks!
./mvnw clean install