Any update on Sismo? Is it that you may not release it as open source? Or is it just that you are still working on it? Either one is fine, obviously, since it's your project. But, I'm just trying to decide whether I should set something else up. It's been a year since this thread, and I'd rather have a real CI server rather than running it at the shell all the time :)
Thanks! Jeremy Thomerson On Tue, Jul 7, 2009 at 12:53 AM, Fabien Potencier < [email protected]> wrote: > > It is not ready yet. > > Fabien > > -- > Fabien Potencier > Sensio CEO - symfony lead developer > sensiolabs.com | symfony-project.org | fabien.potencier.org > Tél: +33 1 40 99 80 80 > > > Jeremy Thomerson wrote: > > Any chance that we can even get a snapshot of it right now? I would > > like to get continuous integration running for our Symfony projects, > > and was just experimenting with Hudson using the info found at the > > blog post below [1]. It worked well and set up easy, but there are > > other features that would be nice (details on what test failed, etc.) > > > > [1] - > http://jlcoady.net/symfony/basic-continuous-integration-server-with-symfony-and-hudson > > > > Jeremy Thomerson > > > > On Jun 15, 9:31 am, Fabien Potencier <fabien.potenc...@symfony- > > project.com> wrote: > >> Fabrice B wrote: > >>> It is definitely a very sexy tool ! > >>> Since we have started developing something equivalent on our side at > >>> Theodo, with a few complementary features but without the neat web > >>> interface, I would be happy to have an estimate of when you think you > >>> will release it. I would love to be a very active contributor if I can > >>> help ! > >> The code is now pretty stable. I'm working on fixing all the possible > >> edge cases we encounter at Sensio. Expect a first version (without any > >> proper documentation) by the end of June. > >> > >> > >> > >>> We were actually wondering what your strategy was when the test suite > >>> fails, not because of a bad test but because of a problem in the > >>> update process ? For example a change in the svn:externals which > >>> usually breaks the update. Can you correct the update problem, rune > >>> the test suite again and tag the revision as OK ? > >> I don't update the code. As I want to start from a clean state, Sismo > >> exports the project each time it builds it. It takes more time but it is > >> safer and you don't have to deal with edge cases. > >> > >> Fabien > >> > >> > >> > >>> Fabrice Bernhard > >>> -- > >>> http://www.theodo.fr > >>> http://www.allomatch.com > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google Groups > "symfony developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -~----------~----~----~----~------~----~------~--~--- > > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
