Jenkins build pipeline resets objectstoreV2 value on Cloudhub

userQsll 0
Viewed 27

I have a build pipeline building a Mulesoft API and deploying it to cloudhub. The API is using ObjectStore 2 and running on 4.4.0 version.

I am noticing that each time I deploy through Jenkins pipeline, the objectstore flag is getting reset and it is reproducible each time.

We are on Jenkins v2.220 (a bit old for sure), Maven 3.4, ObjectStore Mule plug in v 1.2.1.

It is really annoyinig as we see the log in Cloudhub mentioning that CI server has modified the objectstore property but can't see anything being set through commands visible on pipeline configuration. Mulesoft support team can also only see what I see in the audit logs.

Has anyone faced similar situation and is aware of the root cause? Any pointers would also be helpful.

maven-3 mulesoft jenkins-pipeline jenkins
1 Answers

Mule Maven Plugin 3.3.5 is very old at this time. Many new releases have been made since its release that fix several bugs, including one related to the default Objectstore v2 configuration. Also security vulnerabilities fixes. Try with to update to the latest available version of the Mule Maven Plugin. You can find the information about the latest release and all release notes at https://docs.mulesoft.com/release-notes/mule-maven-plugin/mule-maven-plugin-release-notes

aled0
Related