CASE STUDY: Constant hassle with Jenkins CI

Mooncascade is a leading software and product development company in Estonia. Mooncascade works with local and international customers, mainly in the telecom, defense, finance and startup sectors across the Europe and is often brought on board when companies need to set up an innovation arm and do rapid prototyping.

  • Industry: Computer Software
  • Headquarter: Tartu, Estonia
  • Company size: 70

Challenge: Constant hassle with Jenkins

The real problems with Jenkins started when Mooncascade iOS team needed to migrate their code to the newest Swift version in Xcode. For them it basically meant that they had to provide an extra server, configure the project to be built on machines and hire a DevOps “Jenkins pro” to manage the hardware and software.

“It took us days to get our projects up and running with Jenkins.”

“First, you have to configure build scripts and then set up the environment with all the necessary webhooks and project repositories,” explains iOS developer Alvar Hansen. “We always had to find a setup for similar projects, but we could never be sure that the build environment and configured plugins were error-free. And in case of integration errors, we had to look for solutions from open source communities.”

Read more: The costly maintenance side of Jenkins CI

Solution: Let Nevercode do the annoying part

Getting all the projects up and running and managing the code signing certificates requires a  heavy load of system administration. Nevercode took the responsibility for the annoying part that the iOS developers did not want to spend their precious time on that is managing multiple build servers and software versions. 

“Managing hardware and software on build servers was not our problem anymore. It was Nevercode’s problem. Actually, in that sense there was no problem anymore.” –  Alvar Hansen, iOS Developer

Result: No more code signing problems

“All our code signing problems are solved – for real!”

Project setup with Nevercode is extremely simple. Compared to Jenkins, it’s super easy to see the information about the build environment. Nevercode’s UI allows you to see what kind of features and plugins you may configure for your project.

“All you have to provide is a repository URL, provisioning profiles and signing certificates, and the project is up and running! There is no extra stress about conflicting projects. It’s all done automatically,” – Karl Puusepp, iOS developer at Mooncascade.

Read more: What we learned analyzing more than 75k Nevercode CI/CD builds.

Leave a Reply

Your email address will not be published. Required fields are marked *