In addition the output in 'p4 changes -m1' can trip up log analyzers which fail builds when error messages are detected. Would be good if this was also hidden from the log. For example this is from a standard polled freestyle job:
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building on master in workspace /var/lib/jenkins/workspace/00640681_Polling_Exclude_User
Executor number at runtime: 0
(p4):cmd:... p4 login -s
p4 login -sUser super ticket expires in 5 hours 15 minutes.(p4):stop:3
(p4):cmd:... p4 client -o jenkins-master-00640681_Polling_Exclude_User-3
p4 client -o jenkins-master-00640681_Polling_Exclude_User-3(p4):stop:4
(p4):cmd:... p4 info
p4 info(p4):stop:5
(p4):cmd:... p4 info
p4 info(p4):stop:6
(p4):cmd:... p4 client -o jenkins-master-00640681_Polling_Exclude_User-3
p4 client -o jenkins-master-00640681_Polling_Exclude_User-3(p4):stop:7
(p4):cmd:... p4 counter change
p4 counter change(p4):stop:8
(p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-master-00640681_Polling_Exclude_User-3/...
p4 changes -m1 -ssubmitted //jenkins-master-00640681_Polling_Exclude_User-3/...Change 89712 on 2020/04/15 by super@test_ws 'Fix Error Message: FATAL ERROR at line 1234'
The above 'FATAL ERROR' in the changelist description would fool the paser.