As a result of the program launched by Microsoft in 2019 and now completed Technical conversion of the ERP system "Business Central" (formerly "Dynamics NAV"/Navision) to Extension apps and the associated outsourcing of the source code enable the use of new, modern Tools that cover the entire software lifecycle, from development (VS Code, Docker) to version control (Git) and deployment (Azure DevOps, ALOps).
A central role here is played by DevOps. DevOps stands for a new culture of collaboration between previously separate departments. Shared processes and technologies enable more effective and efficient collaboration between the software development (Dev), system administrators (Ops), but also quality assurance. DevOps can improve software quality and the speed of development and delivery, thereby increasing customer satisfaction.
DevOps unites people, processes and technologies to create continuous added value.
We have been successfully implementing our customer projects with DevOps for some time now, creating a standardized, audit-proof system infrastructure. By using DevOps, we have not only created a standardized workflow for deployment, but also set new standards with state-of-the-art technology.
Important components of DevOps
In contrast to traditional waterfall development models, DevOps involves iterating through shorter software development cycles. DevOps impacts all phases of the application lifecycle Each phase builds on the others, and none of the phases are role-specific. In an ideal DevOps culture, each role is involved in each phase to some degree.
Plan → Develop → Provide → Execute
Tools in the DevOps environment
Planning toolsJira Software, Azure Boards
Coding toolsVS Code, Visual Studio
Source code managementAzure Repos (Git)
Build/release pipelines (Continuous Integration - CI, Continuous Deployment - CD): Docker, Azure Pipelines, ALOps
Wiki/documentation tools: Confluence
Support tools (feedback): Jira Service Management
DevOps steps and systems involved
Feature request: Submitting a customization request via the ticket system (Jira Service Management) by the customer KeyUser
Planning Development taskResource allocation and scheduling of the development task by the project manager (Jira Software)
Programming and functional testsProgramming the adjustments (VS Code) + provision/functional tests (Business Central development system – Access for developers only)
Conclusion DevelopmentDeveloper checks the changed code via "pull request" in the version management (Git). Review and approval by 2nd developer according to the "4-eyes principle"
Build/release pipelines ensure automatic provision of the customer-specific apps in the test/QA system
Acceptance test: The new features are tested in the QA system. If the test is successful, the customer approves the GoLive. In the event of errors, steps 3-6 are repeated.
After GoLive release by customers: Automatic app provisioning in the production systemThis can be done on demand or time-controlled (in a defined maintenance window, e.g. after 18:00) so as not to disrupt live operation
Would you like to learn more about the use of DevOps?
Get in touch with us! Our consultants will be happy to support you or answer any initial questions you may have.
Tel.: 089 - 211 11 848 or e-mail to vertrieb@br-ag.com.
