Upgrading Gradle

Hi all,

This morning I got stopped in my tracks after a Docker for Mac update seemed to stop my Services from building. It’s in #help.

While it seems unrelated, the way to fix this was actually to upgrade Gradle, which we haven’t done in quite some time. To fix the bug I was experiencing, and upgrade a bit of our stack which we haven’t touched in awhile, I updated Gradle (from v2.13 to v4) as well as RAML-Cop (v3 to v5) in openlmis/dev and released openlmis/dev:3.

With such a large jump in Gradle, inevitably there will be Services which won’t build right anymore. I updated Reference Data Service to use openlmis/dev:3 and this is what I needed to do:

https://github.com/OpenLMIS/openlmis-referencedata/commit/d51f2929b0eba6ba16d27034069d1bc3097c54bb

That seems to be all that was needed there which is pretty simple.

I also updated the template service, as it’s good to try to keep it up to date:

https://github.com/OpenLMIS/openlmis-template-service/commit/bb8ef175e80f959f494de58bc19b7489a49735a6

And this too seemed to go smoothly.

Updating every service to use openlmis/dev:3 isn’t a very high priority, especially with a coming Reference Distro release, however it’d be good to start doing so (especially as the latest docker release seems to expose some old Gradle/Cucumber issues). Since Reference Data and the Service Template both were so easy to upgrade, I’d like for the component leads of each Java service to start attempting/scheduling work of updating their Services to openlmis/dev:3, and if any new build warnings pop-up, lets try to problem solve in this thread. With an eminent release of Ref Distro coming and not having the time to fit this into normal sprint planning, lets see what we can do, but not block ourselves.

Best,

Josh

A quick addendum, when following the previous commit around the generateMigration task in build.gradle, you should use this version of generateMigration: https://github.com/OpenLMIS/openlmis-referencedata/commit/d89e25bf99cf5cb1f66b6cf0838fe1eeae8ed36b

This has been done already for services that have made the previous change.

  • Josh
···

On Monday, July 3, 2017 at 1:28:34 PM UTC-7, Josh Zamor wrote:

Hi all,

This morning I got stopped in my tracks after a Docker for Mac update seemed to stop my Services from building. It’s in #help.

While it seems unrelated, the way to fix this was actually to upgrade Gradle, which we haven’t done in quite some time. To fix the bug I was experiencing, and upgrade a bit of our stack which we haven’t touched in awhile, I updated Gradle (from v2.13 to v4) as well as RAML-Cop (v3 to v5) in openlmis/dev and released openlmis/dev:3.

With such a large jump in Gradle, inevitably there will be Services which won’t build right anymore. I updated Reference Data Service to use openlmis/dev:3 and this is what I needed to do:

https://github.com/OpenLMIS/openlmis-referencedata/commit/d51f2929b0eba6ba16d27034069d1bc3097c54bb

That seems to be all that was needed there which is pretty simple.

I also updated the template service, as it’s good to try to keep it up to date:

https://github.com/OpenLMIS/openlmis-template-service/commit/bb8ef175e80f959f494de58bc19b7489a49735a6

And this too seemed to go smoothly.

Updating every service to use openlmis/dev:3 isn’t a very high priority, especially with a coming Reference Distro release, however it’d be good to start doing so (especially as the latest docker release seems to expose some old Gradle/Cucumber issues). Since Reference Data and the Service Template both were so easy to upgrade, I’d like for the component leads of each Java service to start attempting/scheduling work of updating their Services to openlmis/dev:3, and if any new build warnings pop-up, lets try to problem solve in this thread. With an eminent release of Ref Distro coming and not having the time to fit this into normal sprint planning, lets see what we can do, but not block ourselves.

Best,

Josh