The continuous integration at inspectIT is realized using Jenkins. (http://jenkins.inspectit.rocks/)
| Info | ||
|---|---|---|
| ||
In the beginning at least some jobs will stay on NovaTec internal Jenkins server, currently this is:
|
With Atlassian providing us with an Open Source no cost Cloudversion of a Bamboo master server, we use this technology for continuous integration tasks. The build nodes are Amazon EC2 instances, sponsored by NovaTec GmbH (see /wiki/spaces/IN/pages/1867778).
Current jobs on Bamboo
| Job | Link to Bamboo |
|---|---|
| DVDStore Release | https://inspectit-performance.atlassian.net/builds/browse/DVD-DVD |
Meaningful usage of EC2 in Bamboo
- We automatically shutdown EC2 instances in Bamboo after the builds are run (you can also shut the instances down manually)
- We configure to use spot instances whenever possible for building things.
This said, if we see that we need more power or cannot wait for spot instances, it is absolutely fine to change the configuration.
...
Setup in EC2
Jenkins is running on EC2. The master will always be available (reserved instance). Build slaves will be automatically started to execute builds. More information on the setup can be found at Jenkins Setup
Sharing with diagnoseIT
Currently the build infrastructure is shared with the research project diagnoseIT (http://diagnoseit.github.io/). This project is run by the same NovaTec Consulting competence group APM that brings you inspectIT. In order to safe costs, hardware is shared (sharing is caring 
).
Usage of Bamboo
As with the other Atlassian software, Open Source project can use the Atlassian Bamboo Master Continuous Integration server free of charge (build nodes will be hosted on EC2). During our initial testing we found out that Jenkins addresses our wishes in a far better way. This is why we stay with Jenkins.