You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 29, 2020. It is now read-only.
I'm trying to parallize more steps, but quickly hit some bottleneck in jenkins where the more parallel steps you have in a build, the slower every step becomes. So rather than taking ~1 seconds to check if a file exists in a step, it now takes 30 seconds, which is unacceptable and unworkable if we want to parallize tasks. Even steps like withEnv, which should be sub-second, now takes multiple seconds.
@magik6k could you help me debug this? I know you have some dark magic powers when it comes to finding bottlenecks!
Found two existing issues in the Jenkins issue tracker:
I'm trying to parallize more steps, but quickly hit some bottleneck in jenkins where the more parallel steps you have in a build, the slower every step becomes. So rather than taking ~1 seconds to check if a file exists in a step, it now takes 30 seconds, which is unacceptable and unworkable if we want to parallize tasks. Even steps like
withEnv
, which should be sub-second, now takes multiple seconds.@magik6k could you help me debug this? I know you have some dark magic powers when it comes to finding bottlenecks!
Found two existing issues in the Jenkins issue tracker:
The text was updated successfully, but these errors were encountered: