On Tue, Jan 7, 2025 at 9:08 AM Kirk Fitzsimons <[email protected]>
wrote:

> i was hoping to see if a developer of the plugin would know, and if a code
> change was required
>

I am not a developer of the plugin, but my offhand opinion is that this is
an invalid scenario: either consolidate your build steps into one pipeline
using a single `node` step, or if the child pipelines really need to be
triggered independently in other circumstances, deal with your problem
differently. (Cache upload/download; more efficient Git clone options; etc.)

-- 
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 visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1wR0cdf26AvPGJgs%3D_B_Adtsd%3DSA5HdrZiKopBVojkpQ%40mail.gmail.com.

Reply via email to