Links above do not work anymore. Must be re-checked.

It worked. The nightlies are sunny now and the documentation was uploaded to docs.mitk.org. I changed every MITK and eMITK job to use CMake 3.17 now and passed --no-tests=ignore to CTest.

CMake 3.17 is out now. I configured the MITK Nightlies to use CMake 3.17 from tonight on and added the new --no-tests=ignore argument to the call of CTest.

Works.

sudo apt install libxcomposite1 libxcursor1

Pushed new branch T27130-RemoveQtVariablesFromDashboardScripts.

Then let's wait until we talked to the Openstack admins regarding Windows instances. If we can have them in the same Openstack project, resource requirements change anyway. If we cannot have them in the same project, we may just want to increase RAM to 160 GB to have 10 Linux build clients.

P.S. :Great :)

Regarding ressources: Say what you prefer. I'll take care. If 7 would mean, we give back CPU resources. It is no problem. CPUs can be overbooked an if we have no machine configured using the CPU it does not cost money.

Was able to (probably) completely provision Ubuntu 18.04 instances for MITK builds with a cloud-config file.

Was able to successfully connect an OpenStack Ubuntu 18.04 to Jenkins via SSH. Currently writing a cloud-config file to provision the instances for MITK.

@kislinsk Could you describe the current status?

Merged! 🎉 Will be available in CMake 3.17.

Windows is now also possible. You have to file a ticket and specify how many Cores/RAM you want to run with windows.

I activated MITK_AUTOCLEAN_EXTERNAL_PROJECTS on Differential and Continuous jobs. Fingers crossed.

Pushed new branch T27042-AutocleanExternalProjects.

I just thought about it could be a good idea to actually do this in our CMake script right in MITK. We can check all sorts of things there before and after external project processing.

Possibly useful Jenkins plugins:

We also have the possibility to modify the Herald rule that triggers the jobs. For example, if the revision summary contains a certain keyword, trigger a complete rebuild instead of an incremental build. Two disadventages are: Revision creators have to be aware of this possibility, and this is not enough as there may be also some other changes on the master branch since the last build on the build client that affect critical files.

Possible entry points in Jenkions job configuration:

Here's my CMake merge request: https://gitlab.kitware.com/cmake/cmake/merge_requests/4258

In CMake, Source/CTest/cmCTestTestHandler.cxx, cmCTestTestHandler::ProcessHandler(), there is a check if the sum of passed and failed tests equal zero. After another pre-check (see below), "No tests were found!!!" is logged as ERROR_MESSAGE. In Source/cmCTest.cxx, cmCTest::Log(), cmSystemTools::SetErrorOccured() is called if the log type is ERROR_MESSAGE.

Reverted the removal as CTest still fails, probably because of no tests in superbuild projects. I think the best way to solve this is to contribute to CMake.

Pushed new branch T27022-RemoveUnusedSubprojects.

+1 for accessing the script online for Azure.

Currently, the script is unfortunately the only option until Qt 6 possibly introduces package management. BTW, we should create a CI or FS-E scripts repository were I can push my script. Currently I am working on the script to also install the correct Visual Studio runtime on clean clients. Also OpenSSL is included in the latest installers but has to be selected explicitly.