Vert.x 4 GH actions CI

[vietj]

• [x] workflow template that can be reused within the organizations
  • [x] vert-x3
  • [x] eclipse-vert
  • [x] custom SVG icon
• [ ] build requiring customizations
  • [x] vertx-core
    • [x] CI deployed
    • [x] Windows test
  • [x] vertx-sql-client
  • [x] vertx-hazelcast
  • [x] vertx-grpc
  • [x] vertx-web
  • [x] vertx-zookeeper
  • [x] vertx-auth
  • [x] vertx-redis-client
  • [x] vertx-stack
  • [x] vertx-eventbus-bridge-clients
  • [ ] vertx-lang-scala
  • ...
• [x] vanilla builds
  • [x] vertx-codegen
  • [x] vertx-json-schema
  • [x] vertx-tracing
  • [x] vertx-unit
  • [x] vertx-junit5
  • [x] vertx-proton
  • [x] vertx-mongo-client
  • [x] vertx-stomp
  • [x] vertx-service-proxy
  • [x] vertx-dropwizard-metrics
  • [x] vertx-cassandra-client
  • [x] vertx-health-check
  • [x] vertx-rx
  • [x] vertx-consul-client
  • [x] vertx-bridge-common
  • [x] vertx-tcp-eventbus-bridge
  • [x] vertx-amqp-client
  • [x] vertx-camel-bridge
  • [x] vertx-config
  • [x] vertx-kafka-client
  • [x] vertx-rabbitmq-client
  • [x] vertx-mail-client
  • [x] vertx-jdbc-client
  • [x] vertx-mqtt
  • [x] vertx-service-discovery
  • [x] vertx-sockjs-service-proxy
  • [x] vertx-http-service-factory
  • [x] vertx-maven-service-factory
  • [x] vertx-service-factory
  • [x] vertx-circuit-breaker
  • [x] vertx-sync
  • [x] vertx-shell
  • [x] vertx-micrometer-metrics
  • [x] vertx-reactive-streams
  • [x] vertx-lang-kotlin
  • [x] vertx-lang-groovy
  • [x] vertx-codetrans
  • [x] vertx-infinispan
  • [x] vertx-ignite
  • ...
• [x] cleanup files (.travis.yml and .travis.deploy.artifacts.sh)
• [x] add badge to README
• [x] dashboard
• [x] don't cache io/vertx dir in Maven repo

Differences with Travis CI

• each repository has a cron execution of the repository CI action at 4am UTC (previously only vertx-core)
• the entire CI job is executed for PR, previously only the JDK 8 build. This might create contention so it might be changed if it impacts the project development
• builds can run on Windows / MacOS

Dashboard

Project	Status
vertx-codegen
vertx-core
vertx-sql-client
vertx-json-schema
vertx-tracing
vertx-junit5
vertx-unit
vertx-web
vertx-hazelcast
vertx-grpc
vertx-proton
vertx-mongo-client
vertx-stomp
vertx-service-proxy
vertx-dropwizard-metrics
vertx-cassandra-client
vertx-health-check
vertx-rx
vertx-consul-client
vertx-bridge-common
vertx-tcp-eventbus-bridge
vertx-amqp-client
vertx-camel-bridge
vertx-config
vertx-kafka-client
vertx-rabbitmq-client
vertx-mail-client
vertx-jdbc-client
vertx-mqtt
vertx-service-discovery
vertx-sockjs-service-proxy
vertx-http-service-factory
vertx-maven-service-factory
vertx-service-factory
vertx-circuit-breaker
vertx-sync
vertx-shell
vertx-reactive-streams
vertx-micrometer-metrics
vertx-lang-kotlin
vertx-lang-groovy
vertx-codetrans
vertx-auth
vertx-infinispan
vertx-ignite
vertx-redis-client
vertx-zookeeper
vertx-stack

[tsegismont]

On GH Actions, I've noticed we cache the whole repository. On Travis we used to exclude what's in {repo}/io/vertx

This might be the reason we had a failure on GraphQL Apollo tests last week after updating BodyHandler in vertx-web

Perhaps we should do this:

    steps:
      - uses: actions/cache@v2
        with:
          path: |
            ~/.m2/repository
            !~/.m2/repository/io/vertx