BCDevOps Flows for Microsoft Dynamics 365 Business Central

The project is still in development. Please contact me if you want to contribute to this project. !!! UNTIL FIRST STABLE VERSION BREAKING CHANGES CAN HAPPEN WITHOUT ANY ANNOUNCEMENT !!! There won't be any change log or manuals available until the first stable version is released.

How to start

This section describes most important points how to use and configure BCDevOps Flows.

1. Create Azure DevOps Agent Pool and at least one self-hosted Agent
2. Create a fork/clone of this repository
3. Connect Azure DevOps with your fork/clone
4. Configure Azure DevOps variables

Create your first project

This section describes how to start using BCDevOps Flows.

1. Create New BCDevOps Flows Project
2. Add BCDevOps Flows to Existing Project
3. Configure Pipelines

Permissions & Security overview

This section describes all important security/permission settings.

1. Build Service Permissions (Project Level)
2. All pipelines must have access to configured Agent Pool
3. All pipelines must have access to configured Variable Group

Hybrid Deployment

This section describes how to set up BC DevOps Flows, Azure DevOps and Github. Hybrid deployment allows to host your source code in GitHub while maintaining your pipelines and work items in Azure DevOps.

1. Set up GitHub
2. Set up Azure DevOps
3. Configure Pipelines

Important/Interesting setting

The list of supported configuration is available in Settings Overview. Below is a list of the most important setting you should know about or that is different from AL-Go.

• country
• artifact
• versioningStrategy
• writableFolderPath
• artifactUrlCacheKeepHours
• preprocessorSymbols
• removeInternalsVisibleTo
• overrideResourceExposurePolicy

Supported pipeline steps

We strongly recommend to not change any of the standard pipeline or standard scripts. It's highly likely that customized scripts and/or pipelines will be broken in a future update.

You can use the following documentation of supported scripts to build your own pipelines (yaml).

• WorkflowInitialize
• SetupPipelines
• InitNuget
• ReadSettings
• VerifyAuthContext
• DeterminePackages
• IncreaseVersion
• Build
• StoreAppLocally
• PushBackToRepo
• DeployToCloud
• PipelineCleanup

Obsoletion

This section describes future process. This IS NOT YET FOLLOWED and will be active once the project is in stable version.

We will try to not introduce any breaking changes without announcement. However, as the solution depends on external libraries (such as BCContainerHelper) we can not guarantee that there will not be breaking changes caused by other libraries.

For breaking changes not caused by third party libraries, we will announce any such change at least 6 months in advance. We reserve rights to short or even remove this period for any reason.