On Sat, Jul 5, 2014 at 8:06 PM, francis <[email protected]> wrote: > On 07/05/2014 02:46 PM, Ezio Melotti wrote: >> >> 1) a new "Test with buildbot" (or whatever) button is added to the >> tracker next to each patch, and developers/triagers can press it to >> trigger the build; > > > Just an small detail/question: does it make a difference to change the > "trigger the build"-button with a "continuously check this patch" > -checkbox? The idea is not to check when the button is pressed > (if I've understood the original idea correctly) but just to set the > check and from then on get continuously feedback that's (still) working > (e.g. with a small green icon nearby the patch).
The advantage of this is that people can know immediately if a patch still applies (assuming someone checked the checkbox before and that the check runs often enough). However this will waste lot of machine time if no one is looking at the patch for a long time, especially if we consider that there are over 2000 patches currently on the tracker. On the technical side there are two issues: 1) it's easier to send the request whenever someone press the button, rather than having something that keeps track of all the patches that need to be checked and either keeps checking it or keeps sending requests to the buildbot master; 2) the green icon is a good idea, but also requires either a different way for the buildbot master to inform the tracker of the results, or some way to intercept the email send to the tracker and convert it to a green/red icon instead of adding a regular message. A third and simpler option is to just add the icon via JS on the client-side, and possibly also collapse buildbot messages so that they don't flood the message list. > > Regards, > francis > _______________________________________________ core-workflow mailing list [email protected] https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
