New Definition Version on deployment despite no changes

[Ben_F]

Hi,

our Camunda Engine is embedded in a Spring Boot application.
Whenever we deploy this application anew due to our CI/CD-Chain, the engine will (on startup) redeploy the process models on the build path, creating new Definition Versions. We´re now on Definition Version 140 despite only having made 30 changes (we use a version tag to document changes so we know that for sure).
This is quite irritating and I feel like this is not the default behaviour.

Is there some configuration that we accidentally enabled and may disable?

Thanks in advance,
Ben F

[jonathan.lukas]

Hello @Ben_F ,

you can find the solution for your problem here:

Deploy-changed-only behaviour

We are deploying many process definitions as part of a Spring Boot application Camunda version 7.8 (inside the resources folder) In the example that we deploy 2 process definitions invoice.bpmn taxes.bpmn After initial deploy we will have 1 deployment and 2 process instances invoice:1:af4f661d-9980-11e8-b023-026e8d2de89e taxes:1:afb61ae9-9bf5-11e8-9963-0287cf67fc6c If we then make changes to ONLY taxes and redeploy we get a new deployment and 2 new versions invoice:2:afb72c60-9bf5-11e8-9…

Hope this helps

Jonathan