Re: [Pharo-project] Silly Tweet
On Jun 30, 2011, at 3:06 AM, Igor Stasenko wrote:
Another aspect of it, that build servers has a limited space (Marcus has to cut the number of builds , since they taking too much space). While on gforge we can afford to keep much more. Of course keeping latest 'frozen' build doesn't takes too much , except of a little nuisiance after a couple of years every time you open a jenkins, you will see a very long list of jobs, where only few of them actually needed. That's why i thinking that moving things to archive is preferable.
In any way, i think everyone understands that nobody wants to hide existing versions from public eyes. Its only a question of finding appropriate place for them, after development is done.
Yes... we can keep 1.2 a bit. But what I don't want to keep are builds *on top* of 1.2. (the only left now is AIDA, but I removed already some). The amount of project on the build server is already very high: https://pharo-ic.lille.inria.fr/hudson/ and that with almost all 1.2 clients deleted and stuff moved to Jenkins: https://ci.lille.inria.fr/pharo/ But it's fun how something is seen as indespensable that we did not have some month ago (and that some people thought is not important *and* in the Squeak past even actively blocked from happening). How times change... ;-) What this shows is that what Jenkins/Hudson provide is essential, and we should think about to move that somehow deeper into our language... (nice research topic) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
participants (1)
-
Marcus Denker