Change Details

@neher noticed today that MITK Diffusion was not cloned by the CDash script on Linux and subsequently the DiffusionRelease build configuration could not be found. Fallback is the Custom build configuration and hence this is kind of a silent fail unfortunately and I didn't notice it earlier. eMITK is affected as well, @floca. It works on Windows, though. I will fix this as hotfix so it will be available in master and develop branch. You do not have to change anything, the script will update itself. Details: The path given to the git clone command is relative, for example `/home/jenkins/src/eMITK/..`. Windows can resolve this even if the eMITK folder does not yet exist. Linux and macOS seem to actually check and deny the path. This can be fixed with a call to `get_filename_component(path "${path}" ABSOLUTE)` on the working directory before passing it to the git clone command.

@neher noticed today that MITK Diffusion was not cloned by the CDash script on Linux and subsequently the DiffusionRelease build configuration could not be found. Fallback is the Custom build configuration and hence this is kind of a silent fail unfortunately and I didn't notice it earlier. eMITK is affected as well, @floca. It works on Windows, though. I will fix this as hotfix so it will be available on both master and develop branches. You do not have to change anything, the script will update itself. Details: The path given to the git clone command is relative, for example `/home/jenkins/src/eMITK/..`. Windows can resolve this even if the eMITK folder does not yet exist. Linux and macOS seem to actually check and deny the path. This can be fixed with a call to `get_filename_component(path "${path}" ABSOLUTE)` on the working directory before passing it to the git clone command.

@neher noticed today that MITK Diffusion was not cloned by the CDash script on Linux and subsequently the DiffusionRelease build configuration could not be found. Fallback is the Custom build configuration and hence this is kind of a silent fail unfortunately and I didn't notice it earlier. eMITK is affected as well, @floca. It works on Windows, though. I will fix this as hotfix so it will be available inon both master and develop branches. You do not have to change anything, the script will update itself. Details: The path given to the git clone command is relative, for example `/home/jenkins/src/eMITK/..`. Windows can resolve this even if the eMITK folder does not yet exist. Linux and macOS seem to actually check and deny the path. This can be fixed with a call to `get_filename_component(path "${path}" ABSOLUTE)` on the working directory before passing it to the git clone command.