[core-workflow] Use buildbot to test tracker patches

Antoine Pitrou antoine at python.org
Mon Jul 7 15:55:38 CEST 2014


Hi,

Le 05/07/2014 08:46, Ezio Melotti a écrit :
> I recently had a chance to learn a bit more about buildbot, and it
> occurred to me than adding a new builder for testing tracker patches
> shouldn't be too difficult.
>
> This is how it should work:
>    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;
>    2) the buildbot builder receives the URL of the issue and of the
> patch and run all the usual steps with two differences:
>      a) a new step to run "hg import --no-c url_of_the_patch" is added
> after the cloning step;
>      b) an email with the results is sent back to the bug tracker once
> the slaves are done;

I guess the question is: which problem is being solved?

- have tests run faster - that's unlikely, unless we get a very fast builder
- have tests run more reliably - unlikely as well, IMO
- run tests on a different environment - that's useful; but that assumes 
we have a couple different builders which are fast, reliable and with a 
diversity of OSes

Regards

Antoine.




More information about the core-workflow mailing list