[Pharo-project] Increasing bots traffic
Just curious, what is the goal of Jenkins build reports - focus developers attention on failing tests - marketing of the development process Notice I did not say developing the development process ;) Nicolas
On Feb 23, 2012, at 10:46 PM, Nicolas Cellier wrote:
Just curious, what is the goal of Jenkins build reports - focus developers attention on failing tests - marketing of the development process Notice I did not say developing the development process ;)
No idea. and the blue color is so strange :)
Nicolas
On 23 February 2012 22:46, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
Just curious, what is the goal of Jenkins build reports - focus developers attention on failing tests - marketing of the development process
nothing of the above, i think :) It is just a side effect of testing & improving reports from jenkins builds. For me it is clear that those messages should belong to bugs list, not to main list.
Notice I did not say developing the development process ;)
-- Best regards, Igor Stasenko.
Le 23 février 2012 23:01, Igor Stasenko <siguctua@gmail.com> a écrit :
On 23 February 2012 22:46, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
Just curious, what is the goal of Jenkins build reports - focus developers attention on failing tests - marketing of the development process
nothing of the above, i think :) It is just a side effect of testing & improving reports from jenkins builds. For me it is clear that those messages should belong to bugs list, not to main list.
Is there such a bug list?
Notice I did not say developing the development process ;)
-- Best regards, Igor Stasenko.
On 23 February 2012 23:04, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
Le 23 février 2012 23:01, Igor Stasenko <siguctua@gmail.com> a écrit :
On 23 February 2012 22:46, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
Just curious, what is the goal of Jenkins build reports - focus developers attention on failing tests - marketing of the development process
nothing of the above, i think :) It is just a side effect of testing & improving reports from jenkins builds. For me it is clear that those messages should belong to bugs list, not to main list.
Is there such a bug list?
pharo-bugtracker@lists.gforge.inria.fr
Notice I did not say developing the development process ;)
-- Best regards, Igor Stasenko.
-- Best regards, Igor Stasenko.
Ah thanks, http://forum.world.st/mailing_list/MailingListOptions.jtp?forum=3456798 Le 23 février 2012 23:07, Igor Stasenko <siguctua@gmail.com> a écrit :
On 23 February 2012 23:04, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
Le 23 février 2012 23:01, Igor Stasenko <siguctua@gmail.com> a écrit :
On 23 February 2012 22:46, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
Just curious, what is the goal of Jenkins build reports - focus developers attention on failing tests - marketing of the development process
nothing of the above, i think :) It is just a side effect of testing & improving reports from jenkins builds. For me it is clear that those messages should belong to bugs list, not to main list.
Is there such a bug list?
pharo-bugtracker@lists.gforge.inria.fr
Notice I did not say developing the development process ;)
-- Best regards, Igor Stasenko.
-- Best regards, Igor Stasenko.
On 23 February 2012 23:01, Igor Stasenko <siguctua@gmail.com> wrote:
On 23 February 2012 22:46, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
Just curious, what is the goal of Jenkins build reports - focus developers attention on failing tests - marketing of the development process
nothing of the above, i think :)
oh.. not nothing, of course. Yes they should "focus developers attention on failing tests" but for those who paying attention. There's a little sense putting them on main list, since most of people there do not care anyways :)
It is just a side effect of testing & improving reports from jenkins builds. For me it is clear that those messages should belong to bugs list, not to main list.
Notice I did not say developing the development process ;)
-- Best regards, Igor Stasenko.
-- Best regards, Igor Stasenko.
participants (3)
-
Igor Stasenko -
Nicolas Cellier -
Stéphane Ducasse