On Tue, Mar 30, 2021 at 1:21 PM Michael Carter
wrote:
>
> Which of course causes a lot of CPU usage on the master due to the frequent
> lookups to the identical username/password.
I suppose you have already concluded that the high CPU usage is caused
by the abovementioned credential lookups.
This is not really possible. There is
https://github.com/jenkinsci/workflow-cps-plugin/blob/f522e783e917bc0aa0513a29684285b710163905/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java#L357-L387
(which is *not* an API you may use from another plugin) but the `run`
timing
Guess I should have added more context.
I have users adding this type of code to their pipeline scripts.
loop {
retry(10) {
withCredetials {
... some code. that takes about 10ms. or less
}
}
}
Which of course causes a lot of CPU usage on the master due to the frequent
Run `jstack`? Not sure what this plugin is or how it relates to diagnosing
high CPU usage.
--
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
Basically the use case.
We've got a few jobs doing:
loop {
retry(10) {
withCredetials {
... some code. that takes about 10ms. or less
}
}
}
It's eating up 100% CPU on the master. I suspect we have other(s)/cases
of people doing things like this and I'm trying to add a
