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
It seems the bot only got three events for each of the subjobs, so there isn't an event for the parent job. Either we reconfigure Jenkins so that it triggers subjobs as real subjobs (instead of the same job but with different configuration?), or the bot needs to know how to merge the CI links.
Activity
targos commentedon Oct 25, 2022
/cc @gengjiawen
gengjiawen commentedon Oct 25, 2022
This is introduced in #353, not sure the best way to fix it.
joyeecheung commentedon Oct 25, 2022
It seems the bot only got three events for each of the subjobs, so there isn't an event for the parent job. Either we reconfigure Jenkins so that it triggers subjobs as real subjobs (instead of the same job but with different configuration?), or the bot needs to know how to merge the CI links.
gengjiawen commentedon Oct 25, 2022
I am for this one, as long as we can keep the same url and config.
Context: nodejs/node-core-utils@046bc0d.
leuasseurfarrelds247-arch commentedon May 29, 2026