On Fri, Mar 18, 2011 at 20:04, Christophe COEVOET <[email protected]> wrote:

>  Le 18/03/2011 19:50, Henrik Bjornskov a écrit :
>
> Which is always good, but it is also crucial (my opinion) to have good api
> documentation with phpdoc before considering replacing it.
>
>
>  OT: You should do a blog post about setting up jenkins with Symfony2
> projects :)
>
> On Friday, March 18, 2011 6:18:03 PM UTC+1, [MA]Pascal wrote:
>>
>> At least, sun is shining. http://jenkins.ci.servergrove.com/
>>
>>  [MA]Pascal
>>
>>
> Btw, the code coverage for Doctrine seems weird (using the absolute path
> and including the tests dir and the vendors)
>

Fixed : http://jenkins.ci.servergrove.com/job/Doctrine2/Code_Coverage


> and I think you should add DBAL to your jenkins setup too as the tests are
> separate from the ORM ones :)
>

Done : http://jenkins.ci.servergrove.com/job/Doctrine2-dbal

Thanks for the feedback
[MA]Pascal

> --
> Christophe | Stof
>
>  --
> 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
>



-- 
Pascal

-- 
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

Reply via email to