Use E071-CI with Jenkins for our MITK CI system.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | kislinsk | T27016 Use OpenStack for our CI system | ||
| Restricted Maniphest Task |
Event Timeline
Comment Actions
Windows is now also possible. You have to file a ticket and specify how many Cores/RAM you want to run with windows.
Comment Actions
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.
Comment Actions
Was able to (probably) completely provision Ubuntu 18.04 instances for MITK builds with a cloud-config file.
The last thing missing is to mount volumes as home directory to have enough space for building MITK.
We should increase our RAM in the Openstack E071-CI project from 120 to 160 GB, as we cannot effectively use all the other resources with dkfz-8.16 instances (7 instead of 10 instances). Or we can even release other resource allocations if we say that 7 instances are just fine. But the status quo is a waste of idle resources.
Comment Actions
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.
Comment Actions
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.
The instances now boot from volumes based in images instead of booting directly from images. So this task is potentially resolved regarding Linux instances. Let's see if the next Linux builds for rMITK and rDIPP work on these instances. They are up and running.