Closing this meta task. Work will be done in targeted tasks.

Blocked by the fact that e071-jenkins is not yet reachable from outside.

Poor man's backup of the settings: 😄

Note that it's only on Linux as it is the only client where I activated tests. I will disable them for now again and we can decide on Wednesday how we want to proceed.

Damn. As long as the test fail we cannot activate the tests, as reviews will never leave draft state.

Seems to work, but mitkPluginGeneratorBuildTest-Release fails.
http://e071-jenkins:8080/job/MITK/job/Differential/job/Linux/220/consoleFull

Activated tests on Linux Differential clients. Buildable is currently running. If it works as expected, I will also activate the tests for macOS and Windows.
{B605}

I agree that we should have debug clients but not as Continuous, as at least on Windows Clients Debug builds are not faster but at least quite some time slower because of very long execution of tests with lots of image pixel access. Nightly clients in debug mode should make sure not to execute package tests as long as we only support release mode installers.

Sorry, did not see your claim, was already working on it. Proposed fix in D308

Seems the reason this passes on all official clients is Debug vs Release. We currently only test release which ignores asserts. Thus, this should be investigated properly by tracing the problem, Windows and Linux are both affected

Uh, I noticed that it is possible to add aliases/workflows to Arcanist, that are sourced from the project repository. Could be a nice way of streamlining some things. I also noticed that there's already an arc feature feature/T12345-bla which boils down to a git checkout develop && git checkout -b feature/T12345-bla.

Pushed new branch bugfix/T27418-DashboardScriptDownloadWorkaround.

We need specific information of the test failures and if they are the same thing.

Diffusion still shows this:

As noted this seems to be a problem only with Ubuntu-18.04 Debug DiffusionAll because of the mentioned error (so the test itself is not wrong for every system). The accumulated test status is passed. I find this an unsatisfying behavior.

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.