(replies inline) On Fri, 16 Mar 2018, Andrew Bayer wrote:
> If we???re going to be tracking step invocations anyway, it???d be interesting
> to count the number of Declarative Pipelines with a script block, maybe?
I kind of assumed that if we were incrementing a counter on step invocations
that script{} would be collected already by the machinery, e.g. isn't it "just"
a step?
If it's a special snowflake then I'll make sure to include it in my design.
A few more which come to mind now that I'm thinking about Script:
* Count of stages per Pipeline
* Count of Pipelines with the Groovy sandbox disable
* Time spent in script{} block
Thanks for the ideas abayer!
Cheers
- R. Tyler Croy
------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
xmpp: [email protected]
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
------------------------------------------------------
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/20180316213201.ckenekkqcbgtsuzx%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
