Grundfos and Praqma have been close partners since 2007 and have a constant eye on the optimization potential of software development at Grundfos.
Praqma’s knowledge of automation, configuration management and especially best practices is pivotal for Grundfos’ software business.
Approximately 100 software engineers in Grundfos are responsible for new software for each pump variant in Grundfos’ huge product portfolio. The software is used to program and control the pumps and Grundfos releases new versions once or twice every month.
In order to optimize resources, Grundfos wanted to find a method that could automate their processes.
“We wanted to save time and resources and at the same time increase productivity in our software testing. Praqma recommended the open source tool Jenkins CI, which is the Continuous Integration server that continuously integrates all software bits from the software engineers. Next, we introduced automated tool-testing, so that we end up with a version of the software which, in principle, is ready for production. Where it previously took three or four months to conduct a manual test, it now only takes one week. We have optimized our resources by 300 percent and increased our productivity two to three times. These are measurable results that we are very proud of”, says Flemming Ask Sørensen, Project Manager, Grundfos.
Grundfos is inherently unable to upload the new software for its products over the internet and thus cannot deliver software directly to production. However, Grundfos continues to keep a close watch for improvements in their development department.
“We started working with configuration management in 2007, because we needed a tool that could manage the software development in real time in India, China and Denmark - across time zones as well as borders. We were recommended to contact Lars Kruse from Praqma, who has educated us and been a great partner in our work on implementing IBM Rational ClearCase. Three years later, we examined best practices in relation to automating the processes associated with software testing and here Lars and the rest of Praqma once again proved their worth. Their knowledge on Jenkins CI has been a very important element for the results we have achieved”, says Flemming Ask Sørensen.
Since 2007, Praqma has been a permanent Grundfos supplier, and according to Flemming Ask Sørensen:
“Praqma’s strength is that they understand what we want. They have an enormous expertise in handling Jenkins CI and they are very quick to write plugins that work and drive the entire testing process in the configuration system we have chosen. We are in daily contact with Praqma and they are outstandingly good at taking care of things quickly. We greatly appreciate that.”
“A further advantage with Praqma is that they have other similar customers with challenges that we might run into one day. Praqma is a center of excellence and we all contribute input to the Continuous Delivery method. Therefore, there is a great deal of experience exchange that comes with the package we buy from Praqma.”
What testing steps should you include in your Continuous Delivery pipeline? Don’t just string together existing manual processes - use simple, collaborative tools to design something better!
A new card game to design Continuous Delivery pipelines
Continuous Delivery and DevOps are here to stay and not because they’re being practiced by trendsetting unicorn companies. The fact is science tells us that these approaches work and this year’s conference gave us lots of examples.
Continuous Delivery and DevOps - Not Just For Unicorns
A developer that pushes their changes and goes on a celebratory walk to the water cooler is done. But, they’re not done done, their changes have yet to be thoroughly tested, added to future release notes, properly peer reviewed and more. These are pains we want to rid the software industry of, and here’s how we do it.
How we tell the Continuous Delivery story
Immutable infrastructure as code reduces inconsistency and makes deployments faster and easier. We can provision immutable infrastructure with Packer & Terraform. Let’s use them to provision Jenkins Windows build slaves.
An immutable infrastructure approach
The Continuous Delivery and DevOps Conference took place in Stockholm for the third time. It brought together scientists, thought leaders, and practitioners to share their experiences and thoughts on CoDe and DevOps.
Inspiring approaches to Continuous Delivery and DevOps
Only a year ago, I was a CoDe Academy student learning about Git, Docker and Jenkins. This year I’m teaching Docker to 24 students at CoDe Academy 2017 in Aarhus.
Falling in love with Everything as Code and Automation
Hear about upcoming events in Scandinavia, latest tech blogs, and training in the field of Continuous Delivery and DevOps