Correct!
A.
On Tue, Mar 21, 2017 at 1:56 PM, Nick Le Mouton
wrote:
> Thanks Andrew, looks good. So with this patch currentBuild.duration should
> be non 0 and there should be currentBuild.durationString, is that correct?
>
> Nick
>
> On Tuesday, March 21, 2017 at 2:19:18 PM UTC+13, Andrew Bayer
Thanks Andrew, looks good. So with this patch currentBuild.duration should
be non 0 and there should be currentBuild.durationString, is that correct?
Nick
On Tuesday, March 21, 2017 at 2:19:18 PM UTC+13, Andrew Bayer wrote:
>
> And a PR up at
> https://github.com/jenkinsci/workflow-support-plug
And a PR up at https://github.com/jenkinsci/workflow-support-plugin/pull/33
On Mon, Mar 20, 2017 at 6:11 PM, Andrew Bayer
wrote:
> This is more of a general Pipeline matter than just Declarative, fwiw.
> I've opened https://issues.jenkins-ci.org/browse/JENKINS-42952 for this
> and will get a PR
This is more of a general Pipeline matter than just Declarative, fwiw. I've
opened https://issues.jenkins-ci.org/browse/JENKINS-42952 for this and will
get a PR up shortly.
A.
On Mar 20, 2017 15:41, "Nick Le Mouton" wrote:
Hi,
My current jobs use the Slack plugin which notifies a channel when
Hi,
My current jobs use the Slack plugin which notifies a channel when a build
completes, e.g. job name - #2423 Success after 1 min 49 sec. I'm trying to
replicate the same message in declarative pipelines, but I can't seem to
find a way to get the build duration. I have tried using
currentBui
