> Fabien Potencier shew a tool called "Sismo" that we can admire just
> here : http://ci.symfony-project.org/ > Do you know if this tool is available ?
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 !
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 ?
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.
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.)
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.
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.)
> 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.
You could have a look at my symfonyUnderControl plugin which you can
combine with CruiseControl for lime unit tests. It is not completely
finished yet, but the unit testing part at least should work fine.
> 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.)
> 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.
On Wed, 2009-07-08 at 17:21 +0200, Stefan Koopmanschap wrote:
> You could have a look at my symfonyUnderControl plugin which you can
> combine with CruiseControl for lime unit tests. It is not completely
> finished yet, but the unit testing part at least should work fine.
> </shameless self promotion>
> Stefan
> On Tue, Jul 7, 2009 at 12:06 AM, Jeremy
> Thomerson<jeremythomer...@gmail.com> 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.)
> > 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.
> Any news on Sismo availability/timetable by any chance..?
> - Jarno
> On Wed, 2009-07-08 at 17:21 +0200, Stefan Koopmanschap wrote:
> > You could have a look at my symfonyUnderControl plugin which you can
> > combine with CruiseControl for lime unit tests. It is not completely
> > finished yet, but the unit testing part at least should work fine.
> > </shameless self promotion>
> > Stefan
> > On Tue, Jul 7, 2009 at 12:06 AM, Jeremy
> > Thomerson<jeremythomer...@gmail.com> 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.)
> > > 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.
> Same here, really interested in getting an update on this, i cannot
> wait anymore!!! :)
> There is NO decent light solution right now...
> Thanks!
> Kevin
> On Sep 12, 3:02 pm, Jarno Rantanen <jarno.ranta...@mederra.fi> wrote:
> > Hi Fabien,
> > Any news on Sismo availability/timetable by any chance..?
> > - Jarno
> > On Wed, 2009-07-08 at 17:21 +0200, Stefan Koopmanschap wrote:
> > > You could have a look at my symfonyUnderControl plugin which you can
> > > combine with CruiseControl for lime unit tests. It is not completely
> > > finished yet, but the unit testing part at least should work fine.
> > > </shameless self promotion>
> > > Stefan
> > > On Tue, Jul 7, 2009 at 12:06 AM, Jeremy
> > > Thomerson<jeremythomer...@gmail.com> 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.)
> > > > 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.
|
