Skip to content

IT communications

Fully automated releases for three CPU architectures and many distributions.

For an appliance and middleware solution, every release variant is now built automatically: signed, tested and delivered straight to the customer's community.

  • CI/CD
  • Jenkins
  • Ansible
  • Docker
  • Package signing
  • C
  • Java

01

The starting point

Our client from the IT communications industry develops an appliance and middleware solution in C and Java. Every release had to be built for three CPU architectures (x64, armhf and arm64) as well as for different operating systems and distributions, by hand. That cost a lot of time with every release and delayed critical security updates in particular.

02

Our approach

  1. 01 Analysis of the existing build and release process together with the development team
  2. 02 Dedicated build agents for every CPU architecture and target platform
  3. 03 Build pipelines with Jenkins, build environments provisioned with Ansible and Docker
  4. 04 Automatic packaging as .rpm, .deb and .msi, including package signing
  5. 05 Automatic deployment of every release variant to the customer's community

03

The result

  • Every release variant is built automatically for every architecture, operating system and distribution
  • Features and critical security updates are available in a fraction of the time
  • Signed packages that users can trust
  • The team can focus on development again instead of release logistics

Sounds like your project?

Tell us where you are right now. We'll tell you honestly whether and how we can help.

You'll hear back from us within one working day. The first conversation is free and non-binding.