[vtkusers] Testing ITK/VTK/PV contributions with (kitware) Gitlab-CI

[Grothausmann, Roman Dr.]

Many thanks Ben and Dženan for Your replies and pointing me to CircleCI. I see 
that testing contributions employing PV,VTK and ITK all together is rather 
challenging.

I wonder though why my pure VTK (PV) based contribution did not get tested when 
submitted to the VTK-Journal, e.g.
http://www.midasjournal.org/browse/publication/949

Is the testing the VTK/Midas Journals used to do not available any more?

Regards,
Roman

On 08/09/16 16:26, Dženan Zukić wrote:
> Hi Roman,
>
> some of ITK's remote modules are using CircleCI for testing. Two recent examples
> are RLEImage <https://github.com/KitwareMedical/ITKRLEImage> and
> MorphologicalContourInterpolation
> <https://github.com/KitwareMedical/ITKMorphologicalContourInterpolation>. Of
> course, you should be familiar, or familiarize yourself with CircleCI
> <https://circleci.com/docs/configuration/>.
>
> Regards,
> Dženan
>
> On Thu, Sep 8, 2016 at 9:14 AM, Ben Boeckel <ben.boeckel at kitware.com
> <mailto:ben.boeckel at kitware.com>> wrote:
>
>     On Thu, Sep 08, 2016 at 12:36:40 +0200, Grothausmann, Roman Dr. wrote:
>     > Just getting to know Gitlab-CI, I am wondering whether it is possible to test
>     > contributions to ITK/VTK/PV with Gitlab-CI from gitlab.com <http://gitlab.com> or
>     > gitlab.kitware.com <http://gitlab.kitware.com>. As far as I understand, this
>     basically needs runners, in
>     > this case specific to ITK/VTK/PV. Since kitware has done CI even before the use
>     > of gitlab, I wonder if the former testing environments are available for use
>     > with Gitlab-CI and if so how to use them.
>
>     We're (VTK and ParaView) using buildbot to manage our testing. The
>     number of settings we test across machines is hard to specify in YAML
>     files (machines also have different settings based on what you're
>     testing, e.g., load up a different compiler or Qt4 or Qt5 and the paths
>     they live in, etc.). We're working on improving the hardware situation
>     buildbot is currently in; things should be getting better over the next
>     few months on that front.
>
>     > For example, none of my contributions to the ITK/VTK/Midas Journals got into the
>     > testing phase even though marked for testing during submission. So a possibility
>     > to use Gitlab-CI to test the compilation and to run the project test would be
>     > really great, especially for continued development and testing on other OSs.
>     > Specifically, for e.g. testing my FacetAnalyser contribution
>     > (http://www.midasjournal.org/browse/publication/951
>     <http://www.midasjournal.org/browse/publication/951>
>     > https://gitlab.com/romangrothausmann/FacetAnalyser
>     <https://gitlab.com/romangrothausmann/FacetAnalyser>) I would need a runner
>     > environment with PV, VTK and ITK ideally for Linux, MacOS and Windows.
>
>     ITK is using Gerrit and Jenkins, not Gitlab.
>
>     --Ben
>     _______________________________________________
>     Powered by www.kitware.com <http://www.kitware.com>
>
>     Visit other Kitware open-source projects at
>     http://www.kitware.com/opensource/opensource.html
>     <http://www.kitware.com/opensource/opensource.html>
>
>     Please keep messages on-topic and check the VTK FAQ at:
>     http://www.vtk.org/Wiki/VTK_FAQ <http://www.vtk.org/Wiki/VTK_FAQ>
>
>     Search the list archives at: http://markmail.org/search/?q=vtkusers
>     <http://markmail.org/search/?q=vtkusers>
>
>     Follow this link to subscribe/unsubscribe:
>     http://public.kitware.com/mailman/listinfo/vtkusers
>     <http://public.kitware.com/mailman/listinfo/vtkusers>
>
>

-- 
Dr. Roman Grothausmann

Tomographie und Digitale Bildverarbeitung
Tomography and Digital Image Analysis

Institut für Funktionelle und Angewandte Anatomie, OE 4120
Medizinische Hochschule Hannover
Carl-Neuberg-Str. 1
D-30625 Hannover

Tel. +49 511 532-2900