[Plone-testing-team] Mr Roboto (update)

Ramon Navarro Bosch ramon.nb at gmail.com
Mon May 6 09:45:55 UTC 2013


I didnt work on the pull feature, is next step!

Right now takes care about commits/push

El dilluns 6 de maig de 2013, Jonas Baumann ha escrit:

> Hey,
>
> This is great! :-)
>
> Would it be a big deal to also mark the commit / pull-request with the
> status API?
> See: http://developer.github.com/v3/repos/statuses/
> This would make the merge button red when the tests are failed, as with
> travis :-)
>
> Cheers,
> Jonas
>
> Am 06.05.2013 um 00:31 schrieb Ramon Navarro Bosch <ramon.nb at gmail.com<javascript:_e({}, 'cvml', 'ramon.nb at gmail.com');>
> >:
>
> Hey guys,
>
> So finally everything is there :
>
> When a push is done to gh it always notifies mr.roboto and ...
>
> ... it sends a mail to plone-cvs mailing list
>
> ... it checks if the repository and the branch is on any core-dev sources
> ( you can check which repos/branches for each plone version are pinned at :
> http://jenkins.plone.org/roboto/repos ) if its there it starts the
> coredev jobs on jenkins that are involved on that plone versions. It writes
> as a build parameter the information about the commit on jenkins.
>
> ... it checks if the repository and the branch are buildout-coredev repo.
> It starts the coredev jobs on jenkins that are involved on that plone
> versions. It writes as a build parameter the information about the commit
> on jenkins
>
> ... it checks if the repository and the branch are on specific jobs ( you
> can define specific jobs using the UI
> http://jenkins.plone.org/roboto/plips. In this page you can define which
> github repository, branch will checkout, which shell will be executed, and
> for which github repositories branches this job is going to run ). If its
> there it starts a new job ( it'll create if its not there, and reconfigure
> if its there ) with the information.
>
> You can see the list of jobs that are thrown using mr.roboto at :
> http://jenkins.plone.org/roboto/jobs
>
> After Jenkins starts to test it...
>
> ... notifies mr.roboto that this test is going to be run, and github
> commit recived a comment explaining that. Also the jobs url of mr.roboto
> gets the jenkins url for that build.
>
> After Jenkins finish to test it...
>
> ... notifies mr.roboto that this test is finished and writes the results
> on the same github commit comment.
>
> So ... that's all folks, all the code is at :
>
> https://github.com/plone/mr.roboto
>
> It's installed on jenkins master machine and has security mesures on all
> the communitations.
>
> Feedback and comments welcome!
>
> --
> Ramon a.k.a bloodbare
> _______________________________________________
> Plone-testing-team mailing list
> Plone-testing-team at lists.plone.org <javascript:_e({}, 'cvml',
> 'Plone-testing-team at lists.plone.org');>
> http://lists.plone.org/mailman/listinfo/plone-testing-team
>
>
>

-- 
Ramon a.k.a bloodbare
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plone.org/pipermail/plone-testing-team/attachments/20130506/43279640/attachment-0001.html>


More information about the Plone-testing-team mailing list