The workaround resolves the issue. But to apply the workaround, it turns out the easiest way is to drop the existing jobs. It's not clear to me why all of a sudden existing jobs are not replaced during the DSL generation. Also there's no error message signalling the possible reason. I only realized that this is a differentiator between my working tests and failing seed execution after the merge.
Now I took OptaPlanner pipelines as a guinea pig to test this assumption, and after removing existing jobs, the dsl code generation worked correctly. I have triggered nightly build after the DSL generation and the problem is gone. As a result though, the job execution history is lost, including the "age" of a possible test failure. For the sake of timeliness of unblocking nightly builds though, I am gonna replicate this approach for kogito and drools pipelines too. Regards Jan On Mon, 6 May 2024 at 09:25, Jan Šťastný <[email protected]> wrote: > Hello, > it seems that since May 1st the nightly builds fail to trigger due to git > clone error. > > The root problem of this failure is not clear at the moment, but there is > supposed to be a workaround available. I need to figure out how to apply > all across our ASF Jenkins CI jobs. > > Regards > Jan >
