I’m happy to announce that Activiti & Activiti Cloud 7-EA201711 artifacts are out and we encourage people in the community to try them out.
This release was focused on expanding our base building blocks to make sure that they can perform in distributed environments (Docker & Kubernetes).
We added monitoring & tracing capabilities to the platform to make sure that we have visibility when things go wrong.
The following frameworks are now built in in our services:
- activiti-cloud-services-tracing: which currently includes integration with Sleuth and Zipkin
- activiti-cloud-services-monitoring: which delegate to the Spring Actuator the Job to expose metrics for health checks, readyness and liveness probes.
You can find an example of tracing included in our deployment descriptors for Docker Compose & Kubernetes in our [Activiti Cloud Examples Repository](L)
We have also introduced the first iteration of our [Runtime Bundle Security Policies. As described in our RFC document]
The second iteration of Activiti Cloud Connectors was released as well, introducing bidirectional channels by default, which allows our connectors to talk back to Process Runtimes as well as receive IntegrationRequestEvents and send back IntegrationResultsEvents. You can find the source code here: [activiti-cloud-starter-connector]
You can find our published artifacts in [Maven Central]
and our Docker Images have been tagged so you can use the 7-EA201711 tag for each of our images. You can find more details on
[Activiti in Docker Hub]
For December Milestone we want to include 2 new services (building blocks) to deal with Authoring aspects of the platform. For that reason we have two RFCs documents:
We also have an RFC document for our Notifications Service which we plan to have a PoC by the end of the month:
Ping us in Gitter if you want to contribute, give feedack, or if you need help reporting an issue: https://gitter.im/Activiti/Activiti7