What should we do when start a new depolyment by using Camunda plugin for Grails 2

Community Community Extensions
1

What should we do when start a new depolyment by using Camunda plugin for Grails 2?

Our Environment

  1. Grails 2.5.4
  2. Grails plugin: org.grails.plugins:camunda:0.5.0
  3. Camunda workflow engine 7.5.0

What we’ve found
Camunda will auto load the bpmn file when:

  1. New bpmn file added
  2. Existing bpmn file updated

What happened when start a new deployment?

  1. Pulls code from GIT
  2. Uses the code for deployment
  3. There is NO any pre-defined process definitions returned by using repositoryService.createProcessDefinitionQuery().active().latestVersion().list().
  4. Moves all existing bpmn files to other location and moves them back again manually. The same code returns the process definition list as we are expecting.

Our Question
Is there any other option we have to avoid manual bpmn file moving to trigger the auto loading event?

2