Hi,
GSoC coding phrase has begun and I'm implementing a CI bot that runs on
Travis CI and tests pull requests.
My project includes two bots, the CI bot testing pull requests and the
PR bot assigning labels to PRs and notify maintainers.
The design docs are available at https://github.com/l2dy/m
Dear Zero King,
On 4 June 2017 at 14:49, Zero King wrote:
> Hi,
>
> GSoC coding phrase has begun and I'm implementing a CI bot that runs on
> Travis CI and tests pull requests.
>
> My project includes two bots, the CI bot testing pull requests and the
> PR bot assigning labels to PRs and notify ma
On 2017-06-04 14:49, Zero King wrote:
> GSoC coding phrase has begun and I'm implementing a CI bot that runs on
> Travis CI and tests pull requests.
>
> My project includes two bots, the CI bot testing pull requests and the
> PR bot assigning labels to PRs and notify maintainers.
As far as I unde
On Sun, Jun 04, 2017 at 10:23:52PM +0200, Mojca Miklavec wrote:
Dear Zero King,
Thank you very much for the update.
There's one thing I didn't fully understand:
https://github.com/l2dy/mpbot-design/blob/master/cibot.md#interaction-with-ci-bot
"This design is aimed for traceability, we can fi
On Sun, Jun 04, 2017 at 11:13:54PM +0200, Rainer Müller wrote:
As far as I understand it, the CI "bot" are just scripts to be executed
on Travis CI, but the PR bot will be a daemon process running on our own
infrastructure?
Yes, except that the CI bot is not just scripts.
The CI bot is written
