[Insight-developers] [ITK Community] Script for Remote Module testing

[Brian Helba]

Brad,

FYI, I'm going to start running the remote module testing script from
"DASH5.kitware" also on "dash5win7x64.kitware" (which uses Visual Studio
9.0 / 2008), hopefully beginning tonight.

Adding this machine was already part of the plan, but this discussion has
motivated me to finish the configuration. One that Windows build is stable,
we *may* consider moving the Linux coverage of remote modules from
"xiaoxiao-ubuntu.kitware" to "dash5ubuntu.kitware" for the sake of
consistency, but it's not certain yet.

Brian



On Wed, Jan 29, 2014 at 10:53 AM, Bradley Lowekamp
<blowekamp at mail.nih.gov>wrote:

> Bill,
>
> If I add 3 machines to loop through the additional modules, do you think
> it would get too cluttered and un-organized to find the modules with
> problems or the modules you are interested in? How do you find the Slicer
> dashboard for it's modules/extensions?
>
> Brad
>
>
> On Jan 29, 2014, at 10:23 AM, Bill Lorensen <bill.lorensen at gmail.com>
> wrote:
>
> > I prefer keeping the remote module where they are.
> >
> > On Wed, Jan 29, 2014 at 10:15 AM, Jean-Christophe Fillion-Robin
> > <jchris.fillionr at kitware.com> wrote:
> >> +1
> >>
> >> As a side note, we gonna also look at the modular dashboard for Slicer
> >> extension. I think it makes complete sense from an extension or ITK
> module
> >> developer perspective.
> >>
> >> Please, keep us posted of your findings..
> >>
> >>
> >>
> >> On Wed, Jan 29, 2014 at 8:58 AM, Bradley Lowekamp <
> blowekamp at mail.nih.gov>
> >> wrote:
> >>>
> >>> Bill,
> >>>
> >>> That is what I recall from it too. But I was looking at it from an ITK
> >>> developers perspective. I wanted to get the whole ITK view the way I
> was use
> >>> to from the normal dashboard. I am not suggesting replacing the current
> >>> view, well just the moving the "Expected Nightly Remote Modules" there
> as I
> >>> think the current layout won't scale.
> >>>
> >>> As a modular developer the modular dashboard might be the right view. I
> >>> would get a line for my module and I may be able to drill down for that
> >>> module. I don't see a live version of it anymore to check though.
> >>>
> >>> I was just thinking that they might compliment each other for these two
> >>> cases.
> >>>
> >>> Brad
> >>>
> >>> On Jan 29, 2014, at 8:44 AM, Bill Lorensen <bill.lorensen at gmail.com>
> >>> wrote:
> >>>
> >>>> I do not recommend the modular dashboard. It has severe navigation
> >>>> issues.
> >>>>
> >>>> On Wed, Jan 29, 2014 at 8:36 AM, Bradley Lowekamp
> >>>> <blowekamp at mail.nih.gov> wrote:
> >>>>> Hello,
> >>>>>
> >>>>> I'm lazy and want to reduce the maintenance burden on creating a
> >>>>> nightly build to test the remote modules.
> >>>>>
> >>>>> It looks like the script running on "dash5.kitware" is nicely
> grinding
> >>>>> through some remote modules ( and potentially other off by default
> modules
> >>>>> like DCMTK, MINC). I was about to suggest this be some how added
> into the
> >>>>> "dashboard" branch, but now I am seeing the itkmodular_common.cmake
> script
> >>>>> there, which really has a lot of the functionality need such as some
> support
> >>>>> for valgrind and coverage.
> >>>>>
> >>>>> Does it make since to bring back the modular dashboard for these
> other
> >>>>> modules?
> >>>>>
> >>>>> I really just want to be able to specify a list for modules to be
> >>>>> modularly tested on a a couple builds and try to re-use a script to
> do this.
> >>>>> I am trying to figure out what's the easiest way to do this for the
> long
> >>>>> run.
> >>>>>
> >>>>> Thanks,
> >>>>> Brad
> >>>>> _______________________________________________
> >>>>> Powered by www.kitware.com
> >>>>>
> >>>>> Visit other Kitware open-source projects at
> >>>>> http://www.kitware.com/opensource/opensource.html
> >>>>>
> >>>>> Kitware offers ITK Training Courses, for more information visit:
> >>>>> http://kitware.com/products/protraining.php
> >>>>>
> >>>>> Please keep messages on-topic and check the ITK FAQ at:
> >>>>> http://www.itk.org/Wiki/ITK_FAQ
> >>>>>
> >>>>> Follow this link to subscribe/unsubscribe:
> >>>>> http://www.itk.org/mailman/listinfo/insight-developers
> >>>>> _______________________________________________
> >>>>> Community mailing list
> >>>>> Community at itk.org
> >>>>> http://public.kitware.com/cgi-bin/mailman/listinfo/community
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Unpaid intern in BillsBasement at noware dot com
> >>>
> >>> _______________________________________________
> >>> Powered by www.kitware.com
> >>>
> >>> Visit other Kitware open-source projects at
> >>> http://www.kitware.com/opensource/opensource.html
> >>>
> >>> Kitware offers ITK Training Courses, for more information visit:
> >>> http://kitware.com/products/protraining.php
> >>>
> >>> Please keep messages on-topic and check the ITK FAQ at:
> >>> http://www.itk.org/Wiki/ITK_FAQ
> >>>
> >>> Follow this link to subscribe/unsubscribe:
> >>> http://www.itk.org/mailman/listinfo/insight-developers
> >>
> >>
> >>
> >>
> >> --
> >> +1 919 869 8849
> >
> >
> >
> > --
> > Unpaid intern in BillsBasement at noware dot com
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://kitware.com/products/protraining.php
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-developers
> _______________________________________________
> Community mailing list
> Community at itk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/community
>



-- 
Brian Helba
Medical Imaging
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/pipermail/insight-developers/attachments/20140129/4e56c77a/attachment.html>