Oct. 3, 2015
2:38 p.m.
> well⦠Iâm with Marcus here: the real problem is that we shouldnât use the CI as a repository for download images. Yes I understand but now I have to edit my scripts and find what it not working. > Instead, I would keep them in a public file server (pretty much the same we do with Pharo, we do not keep all builds (or versions) in the CI, but all history is available at files.pharo.org. > And we cannot keep this indefinitely because of many reasons (and the fact that INRIA servers are not infinite is one important). > > So, maybe we should make community available some files.pharo.org/contribution where jobs can upload the built versions (not the full history, but at least stable and development versions? would be nice. > that way people can still find their versions and we can reduce a bit the weight of pharo-contribution? > > cheers, > Esteban > >> On 03 Oct 2015, at 09:15, stepharo <stepharo@free.fr> wrote: >> >> >>>>> We removed the Pillar job for Pharo 3 because we introduced an new >>>>> feature not backward compatible. >>>> Why is that a reason to remove the build? You have a configuration, >>>> don't you? >>> I would suggest: move to a separate job that is run much less often >>> and doesn't keep so many old artifacts. That makes it easier to get old stuff running again. >> + 10000 >> >> >> > >