-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Investigate failing nexus badge tests #2347
Comments
I started looking into this one and must confess I'm a bit puzzled. When I run the Nexus tests locally, I get the same above failures (plus 3 additional ones). However, when I look at the last couple daily service test runs (like 27 and 26), it seems like the Nexus tests are passing 🤷♂️ So are the Nexus tests fixed now? |
Huh, I just ran them locally on 58b2765 and everything passes:
Are they still failing for you? We're returning "invalid," so I wonder if the server is returning some invalid JSON or a 5xx error. Has this been ported to BaseService? That might be a good next step; maybe it'll make these less flaky, or at least failing in a way that leaves behind more clues. |
Yeah still failing for me locally. It's definitely still using the LegacyService so porting it to the new model is a good call. Two birds as they say! 🐦 I can get around to this in the near future, and could likely use this as an opportunity to add support for private Nexus' instances as requested in #1699 if that's still needed |
Well porting legacy services looks like it will be fun 😄 if I have questions while working on this, where's the best place for those? should i just tack them on to this issue or do those types of questions/convos happen elsewhere? |
also the tests are passing for me now, so the issue was most likely just my local environment |
We usually recommend they take place on the issue, though the #dev room on Discord is an equally good place! |
I still need to join Discord (never used it before). One thing I've found is that Nexus has a pretty varied set of APIs between 2.x and 3.x versions of the platform, which may be pertinent especially if we want to support private Nexus instances (via self-hosted Shields instances) as requested in #1699 The current Nexus implementation in Shields (using the Nexus 3.x rest API docs can be found here: https://help.sonatype.com/repomanager3/rest-and-integration-api/search-api What I do not yet know is whether a Nexus 3.x deployment will still support those legacy/2.x API endpoints we're currently using. I think I've got a grip on what I'd need to do to port the existing LegacyService to the new Service model, continuing to leverage the Nexus 2.x endpoints. However, it does beg the question of whether we should add support for Nexus 3.x as part of this process (and if so I have some follow up questions 😄) |
Supporting 3.x sounds good but would be good to do as a follow on. Smaller PRs are always easier to work with, and faster! |
Not sure what's up here. The shields.io badge examples look okay.
Ref: #1359
The text was updated successfully, but these errors were encountered: