Stephan Eggermont wrote

Who is dealing with CI? The queue is still growing and nothing seems to finish.

Stephan

Jenkins tells me there are only 4 jobs using any significant amount of space: - FileTree-Pharo30-dev, - Fuel-Stable - Fuel-Development - PharoProjectCatalog2

The total is 43GB, so actually peanuts.

Jobs:43 GB, Builds:43 GB, Locked builds:10 GB, Workspace:21 GB

FileTree-Pharo30-dev 6 GB 6 GB 4 GB 196 MB Fuel-Stable 6 GB 6 GB 251 MB 338 MB Fuel-Development 5 GB 5 GB 363 MB 12 KB PharoProjectCatalog2 5 GB 5 GB 449 MB - Fuel-Serialize-All 1 GB 1 GB - - Versionner 710 MB 710 MB 494 MB 119 MB ...

In November 2013 the config of FileTree-Pharo30-dev was set by Camillo to keep every 10th build no matter what, and to keep every buildd for the past 30 days. And to run every day. At this point in time it seems especially excessive because no one is fixing the failing tests on Pharo 3 latest when loading FileTree from SqueakSource3. I've changed it to only keep the past 3 builds, and only build when either Pharo3 latest is updated or the FileTree repo on SqueakSource 3 is updated. It could probably be deleted entirely. -- View this message in context: http://forum.world.st/pharo-contribution-CI-out-of-space-tp4800325p4800748.h... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Le 20 janv. 2015 à 17:35, Stephan Eggermont a écrit :

Who is dealing with CI? The queue is still growing and nothing seems to finish.

I noticed that in the past. It may happen when no slave is available to execute a specific job. It happens if one or many slave go offline or if a build is stuck and no other executor is available for other jobs. I don't know if there is a good solution to manage that. My opinion is that we should just be sure that a timeout is set to every job. In addition, we could install these plugin: https://wiki.jenkins-ci.org/display/JENKINS/Purge+Build+Queue+Plugin that will ease our life if the queue grows quickly.