Spring Zeebe Deployment and Versioning

Camunda 8 Topics
,
1

Hello,

We’re running a self-managed instance of Camunda 8. We deploy our BPMN processes using the Spring Zeebe @Deployment annotation.

The behaviour I normally see is:

  • when we start our Spring Boot application the BPMN is deployed;

  • If we restart the application and the BPMN hasn’t changed, nothing is deployed;

  • If we restart the application and the BPMN has changed, the new version is deployed and version number incremented.

This is all as expected. However, sometimes when the application is restarted a new version of the BPMN is deployed even if the definition hasn’t changed.

Could someone confirm the behaviour of this annotation? Is there someway to control the deployment more explicitly whilst using @Deployment? We’d like to have our BPMN in source control and deployed when we release a new version of our Job Worker rather than relying on a user manually deploying using Zeebe client.

Thanks.

2

@keensimo Which version of Camunda 8 you’re using?

3

We’re running 8.5.2.

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.