I am happy to announce that Activiti Core and Activiti Cloud Beta4 has been released.
The focus of the Beta4 release was to improve data consistency between the different services and maturity of the new APIs. We improved the way of handling data inside the Query Service (now it also contains Process Definitions and Variables are kept in different scopes for improved performance on query) which lead us to improved coverage on different scenarios. We are looking forward to leverage these changes with the GraphQL extensions that are still experimental, but we are planning to add soon into our release process. As mentioned before, the APIs are getting better and better and as part of our commitment to support a wide range of cloud deployments we included the first iteration of our Conformance Tests and Cloud Conformance Tests suites. These test suites are designed to enable implementors to extend the basic sets to cover their use cases. We believe that this is a “must” if you are planning to leverage a CI/CD approach.
Also a big part of this release was the upgrade to Spring Boot 2.1 and Spring Cloud Greenwich.M3 which we want to keep in sync with our release train.
The fastest way to get started with Activiti Cloud is to use our HELM charts that allow you to deploy all the services to a Kubernetes Cluster by following some simple steps. You can use any tooling that you already use to deploy HELM charts to Kubernetes or you can try Jenkins X. You can take a look at our Getting Started guides:
You can find the full release notes here.
If you are interested in getting started with Activiti Core you can check our examples repository which highlight how the new Runtimes API is used in the context of Spring Boot 2 applications:
If you are interested in getting involved get in touch via Gitter