Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.150.3
All Pipeline plugins pretty much up to date
Description
After the upgrade from 1.8.10 to 1.9 I am seeing strange format changes:
1.8.10
12:25:11 [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ root --- 12:25:11 [INFO] Clean is skipped. 12:25:11 [INFO] Execution of maven-clean-plugin:3.0.0:clean (default-clean) @ root took 0.063s 12:25:11 [INFO] 12:25:11 [INFO] --- maven-enforcer-plugin:3.0.0-M1-MMS1:enforce (enforce-versions) @ root --- 12:25:11 [INFO] Skipping Rule Enforcement. 12:25:11 [INFO] Execution of maven-enforcer-plugin:3.0.0-M1-MMS1:enforce (enforce-versions) @ root took 0.125s
1.9
[2019-03-07T11:40:27.751Z] [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ root --- 12:40:27 [INFO] Clean is skipped. 12:40:27 [INFO] Execution of maven-clean-plugin:3.0.0:clean (default-clean) @ root took 0.049s 12:40:27 [INFO] [2019-03-07T11:40:27.751Z] [INFO] --- maven-enforcer-plugin:3.0.0-M1-MMS1:enforce (enforce-versions) @ root --- 12:40:27 [INFO] Skipping Rule Enforcement. 12:40:27 [INFO] Execution of maven-enforcer-plugin:3.0.0-M1-MMS1:enforce (enforce-versions) @ root took 0.093s
As you can see, the first output of/for a plugin is using a much longer format, whereever this is coming from.
The pipeline in question is using timestamps() in the options block of the pipeline.
Once I enable the new option "Enabled for all Pipeline builds", the problem vanishes!
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- relates to
-
-
- Closed
-