Releases: jenkinsci/platformlabeler-plugin
Releases · jenkinsci/platformlabeler-plugin
Platformlabeler 4.0 🌈
🚀 New features and improvements
- JENKINS-17904 - Allow to configure labels per node (#104) @mawinter69
📝 Documentation updates
- Improve README with additional columns, less data (#103) @MarkEWaite
Platformlabeler 3.5 🌈
🚀 New features and improvements
- JENKINS-59479 - Support Red Hat Enterprise Linux (#102) @MarkEWaite
- JENKINS-59566 - Support Scientific Linux (#101) @mhayen
- JENKINS-59490 - Support Oracle Linux (#98) @MarkEWaite
📝 Documentation updates
- Improve name and description for search on plugins.jenkins.io (#97) @MarkEWaite
📦 Dependency updates
- Use BOM bom-2.164.x:3 for dependencies (#100) @MarkEWaite
Platformlabeler 3.4 🌈
- Add LsbRelease tests & sample platform data (#94) @MarkEWaite
- Require Jenkins 2.164.3 (#93) @MarkEWaite
- Clarify nullabilty of fields (#92) @MarkEWaite
- Consistency check commits with pre-commit hook (#91) @MarkEWaite
Platformlabeler 3.3
🚀 New features and improvements
- Provide plugin documentation from GitHub README (#90) @MarkEWaite
📦 Dependency updates
- Bump plugin pom to 3.49 (#86) @dependabot
- Bump checkstyle to 8.23 (#82) @dependabot
Platformlabeler 3.2
Platformlabeler 3.1
Label Linux agents even without lsb_release
Linux agent labeling prefers the output of the lsb_release command for historical reasons. Many slim and lite verions of operating systems do not provide the lsb_release command (Alpine, Debian Slim, etc.). If the lsb_release command is not found, use the contents of /etc/os-release to approximate the values that would have been returned from lsb_release.
Some Linux distributions (like Arch and Gentoo) do not have a "version", so the package prefers VERSION_ID and uses BUILD_ID from /etc/os-release if VERSION_ID is not set.