salaboy

Activiti: Last week Dev Logs #74

Blog Post created by salaboy Employee on Dec 3, 2018

Last week we worked hard into stabilizing all projects for Beta4. While working on new features and bug fixes we also improve our pipelines and release scripts making sure that as soon as we are doing with merging all the involved PRs we can do Beta4. We are hoping to be able to release by the end of the week and including the remaining set of issues listed in our Beta4 milestone: https://github.com/Activiti/Activiti/issues/2119

 

@CTI777Implemented support for update process properties API with tests

https://github.com/Activiti/activiti-api/pull/57 

https://github.com/Activiti/activiti-cloud-api/pull/37

https://github.com/Activiti/activiti-cloud-runtime-bundle-service/pull/161

https://github.com/Activiti/activiti-cloud-audit-service/pull/92

https://github.com/Activiti/activiti-cloud-query-service/pull/131

@almericoMoving JX example repositories pipelines with updatebot to mergify and Master Jenkins Cluster

@igdianovworked on the stability of pipelines for core and cloud repositories.

@balsaroriworked on tasks variable mappings

@constantin-ciobotaruworked on model verifications for community

@miguelruizdevkept working on the conformance test sets 0, 1 and 2.

@ryandawsonukresolved issueso that we can use spring boot 2.1 without having to enable bean overriding. Updated release scriptsto look for a master branch when develop isn’t present.

@erdemedeirosadded acceptance test covering process definitions on query service. Investigated issue related to messages not being delivered in some cases (problem solved by setting the property "requiredGroups" in the producer, see https://docs.spring.io/spring-cloud-stream/docs/current/reference/htmlsingle/#_producer_properties).

@salaboyattended AWS reInvent and worked with @igdianovto improve our release pipelines which are now integrated with mergify.io

 

Get in touch if you want to contribute: https://gitter.im/Activiti/Activiti7

We are looking forward to mentor people on the technologies that we are using to submit their first Pull Request

Outcomes