-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins ver. 2.60.3
Office 365 connector 2.5
in most my notifications Completion Time == Start Time and that's not true
I seem to see this for all my pipeline jobs and not for old-fashioned ones. this seemed to happen before v.2.5 as well.
that is: Completion Time is correctly displayed in non-pipeline jobs, but in Pipeline jobs this timestamp seems erroneously to be a copy of start time, not the actual completion time.
[JENKINS-46329] Completion Time broken for Pipeline jobs
Description |
Original:
in most my notifications Completion Time == Start Time and that's not true :) I seem to see this for all my pipeline jobs and not for old-fashioned ones. this seemed to happen before v.2.5 as well. that is: Completion Time is correctly displayed in non-pipeline jobs, but in Pipeline jobs this timestamp seems erroneously to be copied from Start Time. |
New:
in most my notifications Completion Time == Start Time and that's not true :) I seem to see this for all my pipeline jobs and not for old-fashioned ones. this seemed to happen before v.2.5 as well. that is: Completion Time is correctly displayed in non-pipeline jobs, but in Pipeline jobs this timestamp seems erroneously to be a copy of start time, not the actual completion time. |
Assignee | Original: Srivardhan Hebbar [ srhebbar ] | New: Out conn [ outconn ] |