As many have probably noticed, there is an in-progress migration to GitLab-CI for VTK. You can see CI jobs at the top of your Merge Request in the “Pipelines” tab. There are still a few builds that have not migrated and are still on buildbot.
Do: test currently talks to just buildbot because there’s no other way to do it. It can talk to CI and buildbot, but the syntax for doing anything more than “test everything” is complicated just going to be confusing during the transition. So until then, it talks to just buildbot. Developers and Maintainers in the VTK project can start jobs on their own from the pipeline tab. There are some exceptions:
- Contributors who are not at least Developers have jobs in their fork; maintainers generally don’t have access to start jobs for them (ping me and I can start them using some sysadmin-like magic)
- Those same contributors cannot start jobs after a
Do: reformatbecause the robot (which does the push) does have permission, so the jobs appear in the vtk/vtk repository. Contributors cannot start these, but Developers and Maintainers can.
See this issue for tracking the remaining migration tasks. Once CI is the only thing testing VTK, contributor documentation will be updated and
Do: test will start talking to GitLab-CI instead of buildbot.