| # |
Feb 18th 2009, 14:14 |
d1rk |
jperras: it can be unrelated to code-coverage... |
| # |
Feb 18th 2009, 14:13 |
jperras |
alkemann: I tend to agree to some extent. for cont. integration to be useful, you need to maintain ~80% or better code coverage at all times |
| # |
Feb 18th 2009, 14:12 |
d1rk |
jperras: thank you. It looks promising |
| # |
Feb 18th 2009, 14:11 |
d1rk |
alkemann: if it is setup once, it makes the devs and all project-related persons happy :) |
| # |
Feb 18th 2009, 14:09 |
alkemann |
to me it sounds a little overkill, but i would be happy for the experience of doing this :) |
| # |
Feb 18th 2009, 14:02 |
jperras |
of course, you need to have the cake shell in your $PATH as well |
| # |
Feb 18th 2009, 14:02 |
jperras |
actually, that might need a little tweak; I'm not sure if the testsuite shell returns an exit value of 1 when a test fails |
| # |
Feb 18th 2009, 14:01 |
jperras |
http://bin.cakephp.org/view/1733483502 |
| # |
Feb 18th 2009, 14:00 |
jperras |
and populate it with the code in the bin: |
| # |
Feb 18th 2009, 13:59 |
jperras |
d1rk: create a pre-commit file in $BOOK_PROJECT/.git/hooks/pre-commit |
| # |
Feb 18th 2009, 13:59 |
d1rk |
jperras: sounds great. could you give me a hint how to do that? |
| # |
Feb 18th 2009, 13:58 |
d1rk |
jperras: oh, really? how do i do that? |
| # |
Feb 18th 2009, 13:58 |
jperras |
and even a pre-commit to make sure your tests pass before you do a push |
| # |
Feb 18th 2009, 13:58 |
jperras |
d1rk: you can implement your own post-commit hooks in git for test running very easily |
| # |
Feb 18th 2009, 13:57 |
d1rk |
maybe, if there is something like a web-callback in thechaw i would deploy it for myself on a test-instance, somewhere.... |
| # |
Feb 18th 2009, 13:56 |
d1rk |
jperras: i see your point, but i do not agree at all. actually every commit should try not to break everything. |
| # |
Feb 18th 2009, 13:56 |
alkemann |
if u set it up, i dont see a problem. but once we got a spec down, this is kinda of a simpe project :) |
| # |
Feb 18th 2009, 13:55 |
d1rk |
jperras: well, i like the idea of having it (actually, i use it on all my projects) because i can have a look if everything turns out as it should be. And well, it is possible to show other people as well, what had been done. |
| # |
Feb 18th 2009, 13:55 |
jperras |
and ci is really only useful for a nearly complete, stable product |
| # |
Feb 18th 2009, 13:55 |
d1rk |
alkemann: it means to have a automatic deployment to a staging-server that is initiated by a commit. |
| # |
Feb 18th 2009, 13:54 |
d1rk |
i thought we could push the latest revision onto a test-server or something on every commit. |
| # |
Feb 18th 2009, 13:54 |
d1rk |
jperras: oh, ok. |
| # |
Feb 18th 2009, 13:54 |
jperras |
two things which bakery does not yet have |
| # |
Feb 18th 2009, 13:53 |
jperras |
d1rk: you need a very well defined api and test cases for that |
| # |
Feb 18th 2009, 13:48 |
alkemann |
a what= |
| # |
Feb 18th 2009, 13:45 |
d1rk |
alkemann: is there something like a continious integration process for bakery2? |
| # |
Feb 18th 2009, 12:56 |
d1rk |
alkemann: a combination of all usually implies (at least a little bit of) quality |
| # |
Feb 18th 2009, 12:48 |
alkemann |
we can use views for popularity was my point as well |
| # |
Feb 18th 2009, 12:48 |
alkemann |
no we want quality measure i meant |
| # |
Feb 18th 2009, 12:47 |
jperras |
if all we want is a popularity metric, there's page views and # delicious bookmarks |
| # |
Feb 18th 2009, 12:45 |
alkemann |
d1rk: though, it's not good data to use quality. just popularity. |
| # |
Feb 18th 2009, 12:41 |
d1rk |
but we could fetch the data to make something of it. there is no interaction between users in that scenario |
| # |
Feb 18th 2009, 12:41 |
d1rk |
ADmad: it is less community as it is not to communicate with others. It is for personal remember-me list. |
| # |
Feb 18th 2009, 12:41 |
d1rk |
alkemann: hehe |
| # |
Feb 18th 2009, 12:40 |
d1rk |
But that way we could highlight more faved articles and/or higher ranked ones. That makes it possible to create richer content-experience |
| # |
Feb 18th 2009, 12:40 |
alkemann |
d1rk: there is lots of stuff on rating in the wiki atm. and jperras has some math degree he wants to use and make some nice formula :p |
| # |
Feb 18th 2009, 12:40 |
ADmad |
i personally dont like so much *community* oriented features |
| # |
Feb 18th 2009, 12:40 |
d1rk |
right now, all articles are of the same weight. That way, it is almost boring to see a long list. |
| # |
Feb 18th 2009, 12:39 |
d1rk |
second: it makes it possible to weight articles that makes it easier to display more interesting articles. |
| # |
Feb 18th 2009, 12:39 |
alkemann |
jperras: sure. there's room :) |
| # |
Feb 18th 2009, 12:39 |
d1rk |
the benefits i see most from it are: person has more connection to bakery as he/she starts to customize or saves (more or less) personal data in it. |