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.
Classes were created and released without licenses.
Testing done
N/A
### Submitter checklist
- [ ] 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.
The years should represent when the license was being licensed up until last edition. As the classes should have been licensed from the start, I propose to retroactively license them.
@Jagrutiti to validate this content.
Description
Classes were created and released without licenses.
Testing done
N/A