I would like to know the best strategy to deploy my Processes via Jenkins. My deployment artifact consists a set of BPMN, DMN and JavaScript files. There are no Java classes. Also, there are so many common JavaScript files that are widely used across process applications.
As per my analysis there are the two options to deploy.
- Deploy via REST:
Here the drawback I could find is, I am not able to do a change only deployment. I have call activities that includes other bpmn files with binding as “latest”. Since these included bpmn files uses script tasks with Script type as “External resource” (referenced with deployment://print.js) , whenever I do a change only deployment, it is not fetching the script files referenced with “deployment://”. I also tried without giving “deployment://”, but it is not working. So, I am unable make a change only deployment for bpmn files that reference external script files as well as script files alone.
- Deploy via Process Application:
Here I was able to do a change only deployment for child workflows included in the call activity as well as script files referenced with external resources (without “deployment://”) independently.
However, in a .NET environment we prefer to use deployment via REST API.
Is there a way we can achieve the same with REST API.