Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

I found one last hint, about a possible interference with ccache , last try ...

I tried several things again, similar to described above, same situation.

All Differential clients include MITK-ProjectTemplate builds.

I reported the cmakebuilder-plugin issue to Jenkins: https://issues.jenkins.io/browse/JENKINS-65893

Deleted branch from rMITK MITK: bugfix/T28546-macOSCatalina-Boost.

Pushed new branch to rMITK MITK: bugfix/T28546-macOSCatalina-Boost.

We also need to fix the Boost binary build on macOS.

Deleted branch from rMITK MITK: bugfix/T28546-macOSCatalina.

Pushed new branch to rMITK MITK: bugfix/T28546-macOSCatalina.

• For now I will disable SWIG (and PCRE) builds on macOS and require it to be provided (for example via Homebrew brew install swig).
• I already renamed everything in Jenkins, Phabricator, and Git hooks
• The macOS codename extraction can be easily fixed adding the backslash to the extraction regex

Started with Ubuntu 18.04 and 20.04 clients by adding the following script before the actual build. This is roughly what we are doing already in the Dashboard script.

Okay, nice. Last question: You currently have both a PhenotypingRelease and a ClassificationCmdApps configuration. The apps of the latter one are also included in the former configuration. Is it fine to just go for PhenotypingRelease then at the cost of a little larger tarball as also the workbench application is included? @schererj

I gave @schererj and @gaoh rights to start the Kaapana MITK build jobs and to read the configurations: https://ci.mitk.org/job/MITK/job/Kaapana/

• FileConverter: Covered by regular release (see MITK Volume below)
• Phenotyping: https://www.mitk.org/download/kaapana/phenotyping/
• Radiomics: Covered by Phenotyping
• FlowBench: https://www.mitk.org/download/kaapana/flowbench/
• MITK Volume: https://www.mitk.org/download/kaapana/workbench/

Okay, nice. Last question: You currently have both a PhenotypingRelease and a ClassificationCmdApps configuration. The apps of the latter one are also included in the former configuration. Is it fine to just go for PhenotypingRelease then at the cost of a little larger tarball as also the workbench application is included? @schererj

In T28302#220479, @gaoh wrote:

The normal WorkbenchRelease configuration should be even better suited for the future...

+1

In T28302#220475, @kislinsk wrote:

@gaoh

I noticed that the only plugins enabled in the "MitkVolume" configuration are the segmentation plugins. Do you explicitly want to have this "slim" version or is the official WorkbenchRelease configuration more sufficient?

Okay. Currently running the first test with the PhenotypingRelease configuration and tag set to v2021.02. So the file name will be automatically versioned and will appear at https://www.mitk.org/download/kaapana/phenotyping/ once the build succeeds.

I would like to have files versioned / with different names. If it's necessary to have a download link that doesn't change I can help with a script to create a "latest" link, had that for MITK nightlies back in the days

To all: Do you want to version files or do you want to simply override existing old installers when generating new ones (which happens with custom set revisions descriptions as done in a few docker files above)?

I noticed that the only plugins enabled in the "MitkVolume" configuration are the segmentation plugins. Do you explicitly want to have this "slim" version or is the official WorkbenchRelease configuration more sufficient?

In T28302#220185, @floca wrote:

And MITK volume (aka the normal workbench) uses the Release build with segmentation=ON

Maybe we should then just label it MITK Workbenches to avoid confusion and reduce (redundant) artefacts.