[Plone-testing-team] Mr Roboto (update)
tschouns at gmail.com
Mon May 6 07:40:56 UTC 2013
This is great! :-)
Would it be a big deal to also mark the commit / pull-request with the status API?
This would make the merge button red when the tests are failed, as with travis :-)
Am 06.05.2013 um 00:31 schrieb Ramon Navarro Bosch <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 :
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Plone-testing-team