JenkinsCI

"For the details of the setup explained in this talk, see http://t.co/7RPbSGEr " #jenkinsci #FOSDEM

— Kohsuke Kawaguchi (@kohsukekawa)2013-02-02 09:39:22

link to blog post http://t.co/msbILMBq #jenkinsci #fosdem

— Jyrki Puttonen (@jyrkiputtonen)2013-02-02 09:38:53

RT @kohsukekawa: "we take test durations from the last run and distribute them to even out th duration" #fosdem #jenkinsci

— Frits van der Holst (@FritsvanderH)2013-02-02 09:36:34

RT @kohsukekawa: "we take test durations from the last run and distribute them to even out th duration" #fosdem #jenkinsci

— Kris Buytaert (@KrisBuytaert)2013-02-02 09:32:18

"Hardening the tests to run in parallel is a significant task" -- @anickelsen on parallelization with #jenkinsCI at #fosdem

— Francois Garillot (@huitseeker)2013-02-02 09:30:00

"Hardening the tests to run in parallel is a significant test" -- @anickelsen on parallelization with #jenkinsCI at #fosdem

— Francois Garillot (@huitseeker)2013-02-02 09:29:42

RT @kohsukekawa: Next talk in #FOSDEM test&automation dev room: Scale your #JenkinsCI build pipeline automatically to minimize test time

— Kokawa Takashi (@Kokawa_Takashi)2013-02-02 09:29:37

With the distribution mechanism and EC2, no matter how many tests you add, you can complete them in the constant time. #jenkinsci #fosdem

— Kohsuke Kawaguchi (@kohsukekawa)2013-02-02 09:26:50

"Once completed, we use curl to #JenkinsCI remote API to collect test results and aggregate them."

— Kohsuke Kawaguchi (@kohsukekawa)2013-02-02 09:25:11

"In this way 12 sets (each about 10 mins) all complete within a minute" #jenkinsci #fosdem

— Kohsuke Kawaguchi (@kohsukekawa)2013-02-02 09:22:56