Process file repository outside Camunda Engine and auto-deploy with changes

I know keeping the BPMN process file in the resource folder of the Spring boot Camunda project gets auto deployed. I also know how to stop the deployment of unchanged files (refer below link).

What if I want to have a different repository, just for BPMN process files and deploy the process whenever there is a change in the existing BPMN file or a new BPMN file is added to the repository.

HAs anyone tried such a thing?

Hi,
I hope there are better solutions to this, but one we’re using is CI/CD (Teamcity). We have a commit vcs trigger set on the repository with the processes/forms/dmn tables and we’re deploying the processes from the folder via rest API, using a custom powershell script to set the files/source/tenant etc.
It’s not foolproof, but since we don’t need to only deploy unchanged (we have several repos for different tenants, so each repo usually has 1-2 processes), it works for us.

1 Like