Camunda deploys BPMN diagram even when not changed

Hello,

I have the following processes.xml file in Java Spring project.

Each tenant has its own BPMN file and a common escalation_handler.bpmn file that is used by all tenants.

The problem is that the escalation_handler process version is bumped every time there is a deployment regardless of whether the escalation_handler.bpmn file is changed or not.

How can I avoid this?

I am using Camunda 7.13.0

I also tried using the property:
<property name="isDeployChangedOnly">true</property>
But, it did not help solve the issue.

<?xml version="1.0" encoding="UTF-8"?>
<process-application
        xmlns="http://www.camunda.org/schema/1.0/ProcessApplication">

    <process-archive tenantId="abc">
        <process-engine>default</process-engine>
        <resource>bpmn/abc/abc.bpmn</resource>
        <resource>bpmn/common/escalation_handler.bpmn</resource>
        <properties>
            <property name="isDeleteUponUndeploy">false</property>
            <property name="isScanForProcessDefinitions">false</property>
        </properties>
    </process-archive>

    <process-archive tenantId="pqr">
        <process-engine>default</process-engine>
        <resource>bpmn/pqr/pqr.bpmn</resource>
        <resource>bpmn/common/escalation_handler.bpmn</resource>
        <properties>
            <property name="isDeleteUponUndeploy">false</property>
            <property name="isScanForProcessDefinitions">false</property>
        </properties>
    </process-archive>

    <process-archive tenantId="xyz">
        <process-engine>default</process-engine>
        <resource>bpmn/xyz/xyz.bpmn</resource>
        <resource>bpmn/common/escalation_handler.bpmn</resource>
        <properties>
            <property name="isDeleteUponUndeploy">false</property>
            <property name="isScanForProcessDefinitions">false</property>
        </properties>
    </process-archive>

</process-application>

By default version will be increased. you can set to false by setting this property to false

false

https://docs.camunda.org/manual/7.14/user-guide/process-applications/the-processes-xml-deployment-descriptor/

isResumePreviousVersions to false.

Thank you @cpbpm for your reply.
However, I don’t think “isResumePreviousVersions” is answer to my question.
Firstly, I don’t understand what it means to: resume the previous deployment?

Also, I want the previous version to remain as is and new version to be deployed only if BPMN file changes.

I tried by adding following anyways just to check its impact. It did not solve my problem. A new deployment happened even when BPMN file was not changed.

false

Hi @yogeshrnaik,

you can use isDeployChangedOnly to configure this.

Hope this helps, Ingo

@Ingo_Richtsmeier
I already tried isDeployChangedOnly but it did not solve my problem.

If the common model is part of several process archives, it will be re-deployed on any change of another diagram in the same process archive. Could that be the case?