4 ms·
Nice summary. Did you test support for handling multiple changes to a single project in parallel? The only CI Platform I've found that tries to handle this in a
by smulc 9y ago
Nice summary. Did you test support for handling multiple changes to a single project in parallel? The only CI Platform I've found that tries to handle this in any meaningful way is OpenStack Zuul (https://zuul-ci.org/ https://zuul-ci.org/) and https://docs.openstack.org/infra/zuul/user/gating.html#testing-in-parallel https://docs.openstack.org/infra/zuul/user/gating.html#testi... for details of the parallel support.
Do others have this need? Or are people generally focusing on keeping CI runs short and landing changes in a serial fashion?
- diggan 9y agoNo, this was not a consideration, as we often have so many PRs open at one time, that this is probably not feasible. If I understand the process correctly, it would merge each PR in order from the first made until the most recent one. So the most recent one includes all the proposed changes. For ipfs/go-ipfs, that would involve doing 104 tests + builds for each PR. Rather, we test each branch as it was merged into master (in isolation), and when master changes, trigger builds for PRs that now are changed. The "Cross Project Testing" and "Cross-Project Dependencies" is something we're deeply in need of though, and already do somewhat. The dependencies are implicit now though (via npm or our golang package manager, gx) rather than explicit. If anyone have ideas for "cross project testing with dependencies" on Jenkins, I would be very happy to hear them.