-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Repo ownership config is not detected when the artifact name and the repo name diverged #531
Comments
I don't think this is a bug in Plugin Health Scoring. This is the normal behaviour. We expect to see the plugin The plugin has some misconfigurations:
All those points to the "old" name. |
Thank you for pointing out the old names. The repo and the team have been renamed over the weekend to match the artifact name, which was changed years ago. |
Repository names and team names can evolve over time without the artifact id changing. An example would be ssh-slaves where it is rebranded with agents in the name, the repository is renamed and likely the team as well |
So you would argue that the team should be composed of the repository name not of the We need to change Line 63 in 1c950c8
context.getRepositoryName() (with some other management as the method returns a Optional<String> but that's feasible.
However, I don't know when I'll be able to work on this. |
I think repository name would be more accurate yeah. |
Noticed on
tikal-multijob-plugin
after the artifact was renamed tojenkins-multijob-plugin
, but the repo itself and the developers team name remainedtikal-multijob-plugin
.The text was updated successfully, but these errors were encountered: