| Summary: | New slaves for Capella HIPP | ||
|---|---|---|---|
| Product: | Community | Reporter: | Christophe Gatti <christophe.gatti> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | denis.roy, hakim.sellou, jean.barata, matthieu.helleboid, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
|
Description
Christophe Gatti
Christophe, I've increased your executors to 4, but your gerrit job runs for 45 minutes, which means you now have multiple Gerrit jobs running at once. I'm not sure how useful that is. Would it be possible to split the build and test operations, remove signing and/or other components that aren't really required for a Gerrit review process, to reduce the run time of the job? Hi, We want do to the opposite, and add tests in the gerrit job. Because, we have more and more external contributions and ours dependencies evolve also very fast. We have 300 000 loc and we want to prevents from regressions, specially in maintenance branches, as soon as possible. So, maybe tomorrow, we will had code coverage or technical debt analysis in our Gerrit job. We don't want to use Gerrit uniquely for code review, but to check a maximum of things before merge in prod branches. But maybe, it's not the good way to do so, do you have any suggestions ? Another thing on slave and executors. We see the 2 new executors, but there are on master only. It' not possible to have a distinct slave, a new machine with the same specs and 2 executors and keep 2 executors on master ? We don't actually have any slaves, other than those used for OS-specific tests ... Every project gets one master with up to 4-6 executors. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. Project-provided slaves are a possibility for CBI, but our default offering is 2 executors. |