On 18 Jan 23:52, Sergi Almacellas Abellana wrote: > >Next thing is the notification, drone is pretty flexible on this: > >http://readme.drone.io/usage/notify/email/ > > > >I find good to notify the author but I feel a little bit concern to > >only > >notify him. What do you think? > > > >Or maybe we could use a new service (or the bug tracker) with a webhook > >to notify the author and others. > > >http://readme.drone.io/usage/notify/webhook/ > We can notify the autor and all the noisy list on the issue tracker.
Yes that's the idea and also we will have a status tracking for the anomaly. > I will like a irc notification on #tryton-commit channel as explained here: > > http://blog.drone.io/2014/3/18/drone-version-0.2.html > > > Do you have any plan to add drone on rietlveld so we ensure that test is > always executed before commiting any changeset? Yes, the first idea was to commit the patch in a staging repository which will be also tracked by drone. So probably setting up a server to receive the webhook will allow also to dispatch the status to the review. But indeed, now that I better know drone. I think it should be possible to get the reviewbot to trigger a build on drone as a Pull Request. But it will require some refactoring on drone for which I already talked about with the maintainer. FYI, this is the drone branch running: https://github.com/cedk/drone/tree/trypod -- Cédric Krier - B2CK SPRL Email/Jabber: cedric.kr...@b2ck.com Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
