https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39877
Jonathan Druart <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |In Discussion --- Comment #80 from Jonathan Druart <[email protected]> --- (In reply to Kyle M Hall (khall) from comment #67) > > Discussion for QA: How should we handle concurrency? > > It's crucial to prevent multiple tests from pushing simultaneously. > > To minimize the risk of the repository becoming outdated, we might need to > > perform > > a pull right before each push. Is that enough? Keep in mind that only one > > job will > > be run at the same time (Koha_Main). > > Maybe later we will also use it for stable branches. > > Should each running specify a name, and maybe a branch? So > koha-ci-results/perltidy > would be koha-ci-results/$branch/$runner/perltidy/$rev Yes, we need to adjust that now, before this gets pushed. Actually it is a problem and we want to catch stuff like bug 40680 (xt/pl_valid.t crashes on U24 only), and the codespell problem described in comment 7. However I don't think it should be $runner. Maybe we need $os: remember that we want RM and RMaints to run those slow tests before they push, and we don't want them to specify the jenkins's job name, we could pass the "OS code" automatically from ktd (D12, D13, U24). > Branch knowability would be a possible issue, `git branch -vv` lists the > tracked branch iirc. Regarding the branch I think we can go with a single "main" branch for now, and list all commit ids. It's a problem we can fix later if it needs to be fixed (and we will create branches on koha-ci-results). -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
