About VTK continuous integration

Development
1

Currently, a full run of VTK continuous integration take more than 24 hours because of long queue time in VTK merge request.

While we try to reduce queue time by selecting which job should run, we recently introduced a new “quick” that will hopefully reduce these as well.

Please use this new stage when running the CI interatively and only run the full CI before merging.

In short that means:

  • Create a MR
  • Ping people for review
  • Do: test -s quick
  • Iterate on review and CI, push again
  • Do: test -s quick
  • Reviewer provide +2
  • Do: test
  • Iterate on CI if needed
  • Do: test
  • Green/Unrelated CI
  • Do: merge

Note: We remarked that sometime previous pipeline are not canceled after a push, do not hesitate to cancel old pipelines.

2 Likes
2

It makes sense. However, it is not clear if this is some temporary measure or it should be followed from now on; and I may forget about using this more complex syntax in a few weeks anyway.

If this is a permanent change in the integration process then it would be more effective to reconfigure do: test to do the quick test. Merging could then require simething like do: fulltest. If fulltest is not executed then the robot could return with a message explaining the developer how to run the full test.

3

Very good remark @lassoan

We wanted to make the default “Do: test” being a quick test but it was more complex to do.

We settled on this as a temporary solution and will reconsider in a few weeks if needed.

You won’t be scolded if you forgot to use the quick stage :slight_smile:

1 Like