Hi all, While cleaning up our Jenkins agents, I noticed that we trigger a lot of long-running (> 1 hr) jobs on a nightly basis. Each family of jobs differs slightly in the gradle task it runs, but there's a lot of overlap. e.g. our 'Solr-Check', 'Solr-Smoketest', and 'Solr-NightlyTests' builds all run our test suite. Combine this with the limited Jenkins hardware we have access to, and it's a recipe for contention.
Nightly jobs alone keep our Jenkins agents pegged for at least half the day! This makes us a bad "neighbor" on these boxes. It also prevents us from firing off ad-hoc jobs or doing anything more inventive or rigorous (like multi-JVMs testing) etc. What do you all think of deduplicating the work done by our Jenkins setup? I'm not attached to any particular breakdown, but one example would be to explicitly run 'test' in the 'NightlyTests' job and then exclude the task from running as a part of the 'Check' and 'Smoketest' jobs. Best, Jason --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
