CamiTK Community Edition merge requestshttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests2020-09-08T11:16:05+02:00https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/119Feature/vtk8 compatibility2020-09-08T11:16:05+02:00Emmanuel PromayonFeature/vtk8 compatibilityVTK8 compatibilityVTK8 compatibilityhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/118WIP: FIXED README spelling2019-07-26T15:40:51+02:00Emmanuel PromayonWIP: FIXED README spellinghttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/117Feature/call actions in action2019-08-04T16:51:42+02:00Emmanuel PromayonFeature/call actions in actiondemonstrates how to call a pipeline of actions in another onedemonstrates how to call a pipeline of actions in another onehttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/116Feature/fix ctest failure2021-01-13T17:47:23+01:00Emmanuel PromayonFeature/fix ctest failureThis branch fixes inconsistent (and unexplained) random test failuresThis branch fixes inconsistent (and unexplained) random test failuresEmmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/115Bug/#842019-05-30T10:04:25+02:00Matthias TummersBug/#84FIXED functions add and remove modified to delete the child components from the maps as well as to delete the components + changed nomenclature for better readability
Closes #84FIXED functions add and remove modified to delete the child components from the maps as well as to delete the components + changed nomenclature for better readability
Closes #84Matthias TummersMatthias Tummershttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/114Resolve "CamiTK property of type double limited to int limits"2019-05-28T23:42:59+02:00Matthias TummersResolve "CamiTK property of type double limited to int limits"Closes #86Closes #86https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/111FIXED add the name of the produced target variable and specify what it is2019-05-09T20:56:31+02:00Emmanuel PromayonFIXED add the name of the produced target variable and specify what it isJust add some information in the CMake macro documentation, nothing fancy...Just add some information in the CMake macro documentation, nothing fancy...https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/110Bug/#622019-05-08T17:03:47+02:00Theophile TiffetBug/#62Should close [issue 62](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/issues/62).Should close [issue 62](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/issues/62).Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/109FIXED separating gitlab runner2019-04-15T21:02:04+02:00Emmanuel PromayonFIXED separating gitlab runnerdebian stable and packaging now have their own runners on two different
VM hosts
What happened :
At one stage, the VM supervisor duplicated the debian stable VM (that had all the gitlab runner installed, registered and running) onto the...debian stable and packaging now have their own runners on two different
VM hosts
What happened :
At one stage, the VM supervisor duplicated the debian stable VM (that had all the gitlab runner installed, registered and running) onto the new debian packaging VM.
After that event there was two gitlab runners, registered using the same token, up and running. Sometimes the debian stable VM gitlab runner took the jobs, and sometimes the new debian packaging VM gitlab runner took the job. If all the jobs of the same pipeline were taken by the same runner, there was no issue and the pipeline succeeded fine. But if, for instance, the debian packaging runner took the check, configure and build jobs, but then the debian stable runner took the test job, then that produced an error.
I deleted the gitlab runner registered on the new debian packaging VM and created a new token and new tag "debian:packaging", just for the packaging.
This branch was created to update the .gitlab-ci.yml file so that the packaging stage/job is exclusively going to run on the new debian packaging VM.
Hopefully that was the last of our pipeline problem to solve!Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/108WIP: Resolve "Bug in refreshInterfaceNode in Explorer.cpp"2019-03-13T21:43:29+01:00Emmanuel PromayonWIP: Resolve "Bug in refreshInterfaceNode in Explorer.cpp"Closes #84Closes #84https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/107Feature/vtk7 compatibility2019-03-01T08:08:37+01:00Emmanuel PromayonFeature/vtk7 compatibilityThe aim of this branch is to provide transparent VTK7 support for the develop branch:
- if you have VTK6 installed on your machine, everything should work like before
- if you have VTK7 installed on your machine, everything should work t...The aim of this branch is to provide transparent VTK7 support for the develop branch:
- if you have VTK6 installed on your machine, everything should work like before
- if you have VTK7 installed on your machine, everything should work too, with a few more disabled test
Some tests need to be disabled when using VTK7 because as for now we cannot manage multiple version of expected output files (and therefore files that are saved using VTK7 differ from the expected files that were saved using VTK6)
Directory `sdk/cmake/ctest/testdatavtk7` contains the expected files that were saved using VTK7.
When CamiTK develop move to VTK7, just move the files of this directory to their respective location. All tests will
then pass.
ThisEmmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/106WIP: Feature/python binding2020-03-06T11:43:04+01:00Emmanuel PromayonWIP: Feature/python bindinghttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/105bug/xvfb-erratic-access2019-01-31T13:51:51+01:00Emmanuel Promayonbug/xvfb-erratic-accessEmmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/104Bug/xvfb erratic access2019-01-30T23:23:29+01:00Emmanuel PromayonBug/xvfb erratic accessCloses #80 (and hopefully closes the bug with it...)Closes #80 (and hopefully closes the bug with it...)https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/103Bug/gitlab runner breaks ci2019-01-30T12:45:53+01:00Emmanuel PromayonBug/gitlab runner breaks ciCloses #79Closes #79https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/102WIP: Resolve "Changing description in automatic actions"2019-01-25T12:02:12+01:00Emmanuel PromayonWIP: Resolve "Changing description in automatic actions"Closes #74Closes #74https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/101Resolve "change the Q_PLUGIN_METADATA(IID ... string in cep wizzard"2019-01-25T13:51:15+01:00Jean-Loup HaberbuschResolve "change the Q_PLUGIN_METADATA(IID ... string in cep wizzard"Closes #76Closes #76https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/100FIXED continous integration2018-10-06T16:09:58+02:00Emmanuel PromayonFIXED continous integrationTrying to fix a strange/unexpected regression introduced
since branch feature/improve-CI-packaging-log
(or introduced by a side effect of the debian machine
configuration?)Trying to fix a strange/unexpected regression introduced
since branch feature/improve-CI-packaging-log
(or introduced by a side effect of the debian machine
configuration?)https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/99UPDATED improve output of packaging summary2018-09-26T16:25:13+02:00Emmanuel PromayonUPDATED improve output of packaging summaryhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/98Debian Packaging Continuous Integration2018-08-02T16:46:49+02:00Emmanuel PromayonDebian Packaging Continuous IntegrationAdd debian packaging as a stage of the continuous integration. Should be run regularly (once a week?), not for each commit/push Add debian packaging as a stage of the continuous integration. Should be run regularly (once a week?), not for each commit/push