[email protected] schrieb am Mittwoch, 3. September 2025 um 11:28:54 UTC+2:
Thank you for your reply Maciej. However, I don't think I have the same problem you are describing since no artifacts are being archived into Jenkins itself, we archive things in Nexus at a later stage. Additionally, as I said, the nightly jobs, which are equal to the changes validating, aren't being affected by this slowdown. At the moment, I'm convinced that this a problem with either the change discovery done by Gerrit Trigger Plugin, or a load problem (less so of this option, because doubling our resources had virtually no effect on the problem). Gerrit trigger does not 'discover changes', it listens to stream events (at least in the normal setup). You can configure it o wait for replication to also finish, which can introduce a certain lag (depending on how your gerrit replication instance is configured, e.g. with a long replaction delay). If you look at the classic view (not blue ocean / pipeline stages...) you should see timing information: This run spent: 8.8 sec waiting; <== we have a 5 sec. replication delay 8 min 58 sec build duration; 9 min 7 sec total from scheduled to completion If anyone would have any pointers on how to further pursue this issue, I'd be deeply grateful. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/9d3a4faf-ab33-405c-9c19-05b9b5079e49n%40googlegroups.com.
