Deploy-changed-only behaviour


#1

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-9963-0287cf67fc6c
taxes:2:af4e7ba6-9980-11e8-b023-026e8d2de89e

As you extrapolate this example out to a real world example with 10 process definitions, we are required to do alot of unecessary migration

The configuration key deploy-changed-only appears to say that it will handle this problem, meaning that only the changed process definition will be updated to a new version, but what i see in testing is still multiple versions

What configuration or setup is needed such that only changed process definitions will be re-versioned and deployed, such that we only have to migration processes on changed process definitions?

Continuing from the previous example, if we make changes to taxes and redeploy we should have
invoice:2:afb72c60-9bf5-11e8-9963-0287cf67fc6c
taxes:3:af4e7ba6-9980-11e8-b023-026e8d2de89e

processes.xml is attachedprocesses.xml (567 Bytes)


#2

Hi @Wesley_Connor,

the property is isDeployChangedOnly See: https://docs.camunda.org/manual/7.9/reference/deployment-descriptors/tags/process-archive/#configuration-properties

Would you like to give an additional try?

Cheers, Ingo