Before 2018, there was no central DevOps tooling for development and IT teams. Therefore, the teams decided to build a common DevOps environment.
In it, it was important to maintain flexibility for the teams, so it should not be mandatory to use the common DevOps toolstack. Each team should be able to extend the stack with their own tools. For the organization to adopt it, the focus was on ease of use and close integration. The toolstack had to be the path of least resistance.
But DevOps is about so much more than tools. It was also crucial to spread a DevOps culture and best practices within the company.
The team set out to find a solution - and there are quite a few methods and solutions out there due to the complexity and width of DevOps. Some important factors that played in were:
At the time, the teams spent an unreasonable amount of time hosting their own set of tools on company infrastructure. Often these tools were poorly managed, which led to a lot of technical debt and security issues. And as if that wasn’t enough, most teams did not share any knowledge or best practices with other teams.
These are some immediate ways these challenges manifested themselves:
dormakaba selected the Eficode ROOT managed DevOps platform because:
Within Eficode ROOT, Eficode now helps dormakaba host new tools in the DevOps toolstack (Artifactory, CodeSonar, SonarQube, and Xray). But after implementation, dormakaba has concluded that they are not using Eficode ROOT to its fullest extent, and are at the time of this writing, considering expanding usage further.
“We are happy to work with the competent colleagues from Eficode, learning together with them, and always being able to get flexible support from them”. - Christoph Papke, DevOps Evangelist and Damian Jesionek, DevOps Engineer, dormakaba
With their DevOps toolstack managed by the Eficode ROOT team, dormakaba continues to see a wide range of continuous results.
The ultimate goal that has been met is to have a toolstack that is a common foundation for their widely used tools, to support all phases of the software delivery lifecycle. To:
dormakaba currently uses Eficode ROOT to deliver tools for static code analysis (SonarQube), artifact management (Artifactory), and software composition analysis (Xray).
Although the improvements cannot be quantified exactly, performance has clearly improved in the following areas:
All these positives can be directly translated into overall benefits to the business and its ability to maintain a strong position in a competitive industry.
Some of these benefits include:
Working together, dormakaba has found Eficode to be always very flexible and fast in adapting to new needs and requirements. Even difficult topics were quickly discussed and implemented (e. g. involving CodeSonar or a PrivateLink connection).
dormakaba intends to evaluate and introduce even more DevOps tools to be hosted within Eficode ROOT in the future - tools from other DevOps lifecycle stages that can be added. Especially tools for monitoring and analytics, log aggregation, and automated testing.
They are also considering migrating their Atlassian tools - Bitbucket, Confluence, and Jira. And there is a vision of connecting their own Jira Service Desk to Eficode’s. This would further speed up the process of sharing customer issues with the Eficode support team.
Here are some simple recommendations from dormakaba, based on their own experiences: