Profile the Maven build

A few standouts from an unscientific look at the timing log:

• frontend is very slow:

  • frontend-maven-plugin:yarn (frontend: execute yarn test) 25.047s

  • frontend-maven-plugin:yarn (frontend: execute yarn install) 83.193s

  • frontend-maven-plugin:yarn (frontend: execute yarn build) 90.492s

• maven-war-plugin takes about 10 sec in zanata-war

  • it takes another 10 sec twice! in zanata-test-war

  • the above three war invocations are repeated in the integration test phases, and much slower in some cases (slower build node?)

• functional test overheads:

  • cargo-starts takes 120 sec (running wildfly/EAP to boot Zanata, liquibase, etc)

  • cargo-stop takes 12-13 sec (stopping wildfly/EAP)

  • dependency:unpack (unzip mysql) takes 16-20 sec

• static analysis:

  • findbugs takes 10, 20, 50 seconds for some modules

  • duplicate-finder, checkstyle, enforcer checks each take a few sec

  • duplicate-finder and enforcer checks are repeated by the integration test phases (in Jenkinsfile)

  • animal-sniffer takes about 1 second or more per Maven module, 39 seconds across 25 modules

• miscellaneous:

  • the unit test for Jenkinsfile (in build-tools) takes nearly 9 seconds