Triplea: Travis Master Branch Build Failed

[tripleabuilderbot]

Latest master branch travis build #16527 failed.
No release artifacts will be generated until this is fixed.

[tripleabuilderbot]

Build #16527 failed

[tripleabuilderbot]

Build #16527 failed

[tripleabuilderbot]

Build #16527 failed

[RoiEXLab]

Oh: https://status.gradle.com/incidents/q2vq49fndxg0
Looks like a newer java 11 patch is required, TLS 1.0 is no longer supported

[DanVanAtta]

We might be able to add a 'before-install' step to update java: https://travis-ci.community/t/old-java-version-in-bionic/4726

Simplest would be go to jdk12 for all builds, could be a decent temporary measure but would also be reason perhaps to migrate to java12 or java13 (not sure if good idea, maybe better to stay with LTS version).

[RoiEXLab]

Whatever works to get the builds running again, I mean if you have some time to spend, you might want to give github CI a try, looks like Github Actions was finally released ^^

[DanVanAtta]

you might want to give github CI a try, looks like Github Actions was finally released ^^

Indeed, though would be a big migration, maybe even bigger than upgrading java version. We'd want to evaluate as well if that is the long term direction we want, pro's/cons vs travis and the ROI of migrating (it might not be worth it, we do have a working solution for now, even if confronted with this problem right now).

I think the update java commands are perhaps the best path forward without doing a large ad-hoc migration (now).

[DanVanAtta]

I mean if you have some time to spend

Side-note, we should be careful of this mentality. I'm about to go back to work full time, the time I can dedicate to TripleA is going to be counted in minutes and hours soon, not days. We should also be really careful to be focused and use our time well. The amount we have to do, it's enough for a team of 10 to be busy for a year, we need to keep that in mind, failure is an option.

[DanVanAtta]

Just to argue with myself, the reverse mentality of constant quick and 'get-it-done' is also arguably how the TripleA codebase got to be so brittle. I think it's a matter of focus/effectiveness and balancing enough quality that we can make important progress, and not just progress.

I'll give the java update commands a try, we do need to get the builds working..

[tripleabuilderbot]

Build #16548 succeeded.