jenkins-plugin-cli --plugins build-time-blame:75.v44a_51cc97cdd-2.1.0
jenkins-plugin-cli --plugins build-time-blame:74.vc523ec8ce69d-2.1.0
jenkins-plugin-cli --plugins build-time-blame:73.vf11a_807a_94b_5-2.1.0
jenkins-plugin-cli --plugins build-time-blame:70.v5031def3c2e3-2.1.0
jenkins-plugin-cli --plugins build-time-blame:64.vd8f4018a2bbe
jenkins-plugin-cli --plugins build-time-blame:2.0.4-66.v9c41d24c1f64
jenkins-plugin-cli --plugins build-time-blame:2.0.4-65.v671d1c64c6b3
The pom.xml now specifies 2.164.1
which matches the readme. This removes warnings and errors when installing the plugin on some Jenkins versions. Refer to #31.
jenkins-plugin-cli --plugins build-time-blame:2.0.3
Some versions or configurations of the timestamper plugin add two spaces between the timestamp and the log statement. This caused the default ^Finished: (SUCCESS|UNSTABLE|FAILURE|NOT_BUILT|ABORTED)$.*
regex to never match.
This release includes changes from #29 so that leading and trailing spaces are not considered when checking for a match. The readme was also updated to make it clear how the matching works.
jenkins-plugin-cli --plugins build-time-blame:2.0.2
The report will now successfully load when log statements contain newline characters. This caused the report to fail when trying to find timestamps for these lines.
jenkins-plugin-cli --plugins build-time-blame:2.0.1
jenkins-plugin-cli --plugins build-time-blame:2.0.0
jenkins-plugin-cli --plugins build-time-blame:1.2.1
jenkins-plugin-cli --plugins build-time-blame:1.2.0
jenkins-plugin-cli --plugins build-time-blame:1.1.2
jenkins-plugin-cli --plugins build-time-blame:1.1.0
jenkins-plugin-cli --plugins build-time-blame:1.0.3
jenkins-plugin-cli --plugins build-time-blame:1.0.2
jenkins-plugin-cli --plugins build-time-blame:1.0.1