Hi Dynamics Community,
Our client will continue on Microsoft Dynamics NAV 2018 (C/SIDE & C/AL) through end‑2026. We’re researching on implementing a CI/CD pipeline (Azure DevOps/GitHub Actions) and would appreciate your advice on:
Source Control: Object export formats, repo structure, branching for features/hotfixes
Build & Compile: Headless compilation tools (e.g., NavContainerHelper, Automation Toolkit) and error enforcement
Testing: Unit/integration test frameworks and result integration in pipelines
Packaging: Creating/versioning deployable artifacts (.fob/.navx), handling localization
Deployment: Automating app publish, schema sync, data upgrades with rollback strategies
Lessons Learned: Common pitfalls with schema changes, upgrade scripts, and YAML snippets or community extensions
Documentation: Links to any proper guidance or reference materials on CI/CD for NAV 2018
Thank you for any concise scripts, pipeline examples, or tooling recommendations.
Great question—setting up CI/CD for NAV 2018 (C/SIDE / C/AL) is possible, though less streamlined than AL-based extensions. Here's a concise guide based on community best practices:
ExportToNewSyntax=1
.fob
CI NAV 2018
NAV DevOps
Let me know if you'd like a sample YAML or PowerShell pipeline template.
✅ Mark this answer as verified if it helps you.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Rishabh Kanaskar 4,255
Sumit Singh 2,665
Nimsara Jayathilaka. 2,401