Automated Camunda Deployments - CI for process files - Shared Engine

[thorben]

Hi Stephen,

Thanks for providing your code. I really like the idea. Some thoughts on your questions:

@StephenOTT

How can Tests be added? I am looking at jUnit + Cucumber at the moment. In the ProcessProjectTemplate model there are not java delegates or other java code you upload/deploy. Everything is in your Project as Scripts and related files. So the number of unit test use cases are reduced in some respect.

Sounds like a good approach. Maybe it is possible to enable writing steps in Nashorn javascript. Then people can use use your template with very little pure Java knowledge. You could also provide a separate library with common step definitions, for example one that sets up a Mock REST endpoint or similar.

There is already a community extension in the BDD area, see GitHub - camunda-community-hub/camunda-bpm-jbehave: camunda BPM community extension providing support for JBehave testing framework.

@StephenOTT

Thoughts on Migrations?

I haven’t got much to say here. Just be aware that making multiple REST requests (one for deployment, x for migrations) means that the process will not be atomic anymore.

@StephenOTT

A few common helper scripts are documented at: ProcessProjectTemplate/docs/helpers.md at master · StephenOTT/ProcessProjectTemplate · GitHub, would be interested to know of other common scripts that people use.

Here as well, it could be nice to publish these scripts as a separate Maven artifact that people can depend on.

Cheers,
Thorben