[Python-Dev] Automated testing of patches from bugs.python.org

[Wes Turner]

Here's a GerritChangeSource for BuildBot events:
http://docs.buildbot.net/latest/full.html#chsrc-GerritChangeSource

Great idea, thanks again!

On Tue, May 19, 2015 at 1:25 PM, Wes Turner <wes.turner at gmail.com> wrote:

> http://docs.buildbot.net/latest/search.html?q=docker ...
>
> Here's a BuildBot Dockerfile:
> http://docs.buildbot.net/latest/manual/cfg-buildslaves-docker.html#image-creation
>
> On Tue, May 19, 2015 at 1:22 PM, Wes Turner <wes.turner at gmail.com> wrote:
>
>> Cool! Thanks!
>>
>> BuildBot integration?
>>
>> * http://docs.buildbot.net/latest/full.html#source-stamps
>> * http://docs.buildbot.net/latest/full.html#enabling-the-irc-bot
>> * http://docs.buildbot.net/latest/full.html#choosing-a-change-source
>>
>> https://github.com/audreyr/cookiecutter-pypackage (requirements.txt,
>> setup.py, Makefile)
>>
>>    pip install cookiecutter
>>    cookiecutter gh:audreyr/cookiecutter-pypackage
>>
>>
>> On Tue, May 19, 2015 at 10:02 AM, Kushal Das <kushaldas at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> With the help of CentOS project I am happy to announce an automated
>>> system [1] to test patches from bugs.python.org. This can be fully
>>> automated
>>> to test the patches whenever someone uploads a patch in the roundup, but
>>> for now it accepts IRC commands on #python-dev channel. I worked on a
>>> docker based prototype during sprints in PyCon.
>>>
>>> How to use it?
>>> ---------------
>>>
>>> 1. Join #python-dev on irc.freenode.net.
>>> 2. Ask for test privilege  from any one of kushal,Taggnostr,bitdancer
>>> 3. They will issue a simple command. #add: YOUR_NICK_NAME
>>> 4. You can then test by issuing the following command in the channel:
>>>
>>>     #test: BUGNUMBER
>>>     like #test: 21271
>>>
>>> This will do the following:
>>> Start a new job on ci.centos.org, announce it on the channel, and
>>> announce the result also.
>>>
>>> I will be working on a minimal lint for patches, and include it
>>> the workflow.
>>>
>>> The current steps can be found at [2]. Each build is happening on a
>>> fresh system.
>>>
>>> Limitations
>>> -----------
>>>
>>> 1. It excepts one single patch to contain all the required changes
>>> (instead of a series of patches).
>>> 2. It runs only on x86_64 architecture, CentOS7 based systems.
>>>
>>>
>>>
>>> [1] https://ci.centos.org/job/cPython-build-patch/
>>> [2] https://github.com/kushaldas/pypatcher/blob/master/pypatcher.sh
>>>
>>> Kushal
>>> --
>>> Fedora Cloud Engineer
>>> CPython Core Developer
>>> Director @ Python Software Foundation
>>> http://kushaldas.in
>>> _______________________________________________
>>> Python-Dev mailing list
>>> Python-Dev at python.org
>>> https://mail.python.org/mailman/listinfo/python-dev
>>> Unsubscribe:
>>> https://mail.python.org/mailman/options/python-dev/wes.turner%40gmail.com
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150519/593211ee/attachment-0001.html>