On 08/19/2013 06:56 AM, Kinkie wrote: > Hi all, > Now that the matrix jobs feature has matured in jenkins, I'd like to > restructure the jobs we use for our continuous integration testing to > reduce their number.
I have no opinion on the matter because I do not know enough about the problem. You might get more meaningful feedback if you can provide brief answers to the following questions: Why the number of jobs is important, what is the current number of jobs estimate, approximately what number of jobs will we have after restructuring, and what [jobs] are we going to lose as the result of this optimization? Cheers, Alex. > I propose to use these jobs: > - X.Y-matrix -> gcc-only (for now), build a specific revision > - trunk-compilers-matrix -> uses a combination filter to test on any > unix-like platform using any available compiler (gcc, clang, icc, msvc > to come as soon as the windows port reaches stability) > - anybranch-wholefarm-matrix -> same as above, but with some > parameters (a branch to be used, whether to use ccache or not, and an > address to be notified). > > Ideally trunk-compilers-matrix should replace most 3.HEAD-* jobs, > while anybranch-wholefarm-matrix can replace most experimental jobs > (after all, a patch is just a push to lp away). The only nonmatrix > jobs that would remain are > - coverity-submit > - mswin > - possibly some support jobs > > What do you think? > I plan to go ahead on Aug 25th, unless there are no objections. > > Thanks! >
