PCM Development/Build Infrastructure/Infrastructure Operation

Aus SDQ-Wiki
Zur Navigation springen Zur Suche springen

Overview on CI/CD Infrastructure

The infrastructure providing the means to do continuous integration (CI) and continuous deployment (CD) consists of the core components shown in the overview in the following figure. Public access means that the component is accessible to everyone. Internal access means that access is limited to certain IP addresses.



We store all source code in Github repositories. Github notifies the Jenkins build server about every change in the registered Github organizations.


We use Jenkins as build server software. The build server receives notifications from Github and frequently polls changes from the Github organization (e.g. the addition of a new repository). Jenkins creates a build job for every repository containing a Jenkinsfile. If the code of a repository changed, a build is triggered. Jenkins distributes the actual work to worker nodes.


The worker nodes execute the tasks of a build job. Jobs usually are executed within Docker containers. The workers pull the necessary images from a selfhosted docker registry or a public registry.

Docker Registry

To save time during the build, we run a docker registry containing preconfigured docker images.


We run a SFTP server, through which the workers can publish Eclipse artifacts onto an updatesite. The updatesite itself is just a webserver serving the contents of the SFTP server.


Sonatype operates an open source repository for maven artifacts. Workers can deploy built maven artifacts to Sonatype in order to release them to maven central.


All infrastructure components, which contain important data, backup this data to a backup system operated by KIT. We backup all nodes except for worker nodes because they do not persist any important data and are easy to setup. The configuration is covered by the setup protocols references below.

Breakdown of Network Services

The services described above are realized by various applications allocated on various hosts. The following image gives an overview on the involved hosts and applications. We describe the URLs to access the services in the following. Credentials are available in the internal wiki.


Docker Registry
  • accessible via [1] without credentials
  • write access via [2] requires credentials
  • setup protocol and credentials: Docker Registry (internal)
Jenkins Palladio
Jenkins MDSD.tools
Updatesite Palladio
Updatesite MDSD.tools
SFTP Server Palladio
  • only accessible from the institute's subnet via i43vm-docker.ipd.kit.edu:22001
  • login only possible by an authorized SSH key
  • setup protocol: SFTP Server (internal)
SFTP Server MDSD.tools
  • only accessible from the institute's subnet via i43vm-docker.ipd.kit.edu:22002
  • login only possible by an authorized SSH key
  • setup protocol: SFTP Server (internal)
Jenkins Workers Palladio
Jenkins Workers MDSD.tools
Backup Jenkins
Backup Updatesite / Docker Registry
  • Registered groups: org.palladiosimulator, tools.mdsd
  • User account: kitsdq

Maintenance Tasks

  • Responsible: Build Server Managers
  • Virtual machines: regularly install updates
  • Docker images: regularly build up to date images
  • Docker containers: pull and use most recent images
  • Overview on managed applications and VMs (internal)