-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Extension indexer fails to index Gradle-built plugins #42
Comments
@daniel-beck The infra team needs help on this topic, as we have no idea how this project works 😱 (and besides, not sure what to do) cc @MarkEWaite you have been a recent commiter on this project: could you help? |
There's no other issue tracker for this component, so I basically had to file here. I don't expect you to fix this 😉 |
Would it be reasonable to move this issue to the https://github.com/jenkins-infra/backend-extension-indexer/ ?. I'm willing to help, though other priorities will keep me away from this issue until at least November, 2022. I have a draft pull request to that repository #39 to update the tool, but it is draft because my initial smoke testing showed that my modernization attempt may have caused significant damage to the tool. |
Thanks @timja for enabling issue tracking and migrating the issue! |
Service(s)
Other
Summary
https://github.com/jenkins-infra/backend-extension-indexer/ logs at https://ci.jenkins.io/job/Infra/job/backend-extension-indexer/job/master/ indicate failures to index extensions in Gradle-built plugins. They provide an invalid packaging that probably should be ignored or fixed in some manner.
Unknown packaging: jpi
andUnknown packaging: hpi
are keywords to look for.As a side effect, plugins whose build switched from Maven to Gradle disappear from https://www.jenkins.io/doc/developer/extensions/ :(
Reproduction steps
No response
The text was updated successfully, but these errors were encountered: