This project aims to introduce a metric system to calculate the health score of each plugin within the Jenkins ecosystem and reflect the final scores on the Plugin Site for the plugin maintainers and users.
Because it's more difficult to change the artifactId of a plugin, compared to a repository name, the ownership should not be based on the artifactId.
Testing done
Added unit tests to validate the change.
### Submitter checklist
- [x] If an issue exists, it is well described and linked in the description
- [x] The description of this pull request is detailed and explain why this pull request is needed
- [x] The changeset is on a specific branch. Using `feature/` for new feature, or improvements ; Using `fix/` for bug fixes ; Using `docs/` for any documentation changes.
- [ ] If required, the documentation has been updated
- [x] There is automated tests to cover the code change / addition or an explanation why there is no tests in the description.
Description
Closes #531.
Because it's more difficult to change the
artifactId
of a plugin, compared to a repository name, the ownership should not be based on theartifactId
.Testing done
Added unit tests to validate the change.