[vtk-developers] gitlab-push woes
utkarsh.ayachit at kitware.com
Sun Mar 22 09:51:43 EDT 2015
>> 1) Make @buildbot and Do: consistent. It seems odd to do "Do: check" or
>> "Do: merge" and then "@buildbot test". I would expect "Do: test"
> I agree, but currently these are managed by completely different tools.
How about using @robot instead of Do:? That way, we are consistent:
>> 2) Recognition is better than remembering.
How about adding support for 'help' e.g.
And both will come back with a message describing the available
actions and what they do. The first KWrobot check (which gets
triggered automatically) can put a comment saying you can use
"@buildbot help and @robot help for available actions". That way
kwrobot doesn't need to be kept up-to-date with buildbot support
commands (which will evolve -- just this weekend, I added a new
command 'superbuild' to trigger a superbuild from a ParaView merge
More information about the vtk-developers