Leverage internal infrastructure for pulling Docker container images. Reduces pressure on Docker Hub and reduces risk of hitting rate limits.
See #1630.
Instead of letting Spring HATEOAS trigger a build on Commons, and subsequently a build on every data store, culminating in n-builds of REST, instead use this strategy:
* HATEOAS artifactory triggers Commons test, but not build.
* HATEOAS artifactory triggers REST test and build, since it's a direct impact.
* REST is NOT triggered by individual data store builds, since it doesn't directly depend upon them.
Slack notification policy is:
* Signal test failure.
* Signal build failure.
* Signal build success.
By NOT sending a notification for every test success, it should reduce volume of messages. By reducing the number of total builds happening, will also reduce traffic to only chronic failing tests, which we probably need to see anyway. And with number of total builds reduced, should still give us the occasional warm fuzzy when a build DOES complete.
