pekko/.github/workflows/binary-compatibility-checks.yml
Marcos Pereira edb3a654d0
GH Actions: Run validatePullRequest and MiMa (#30557)
* GH Actions: run validatePullRequest instead of just compiling the tests

* Run MiMa checks on GH Actions instead of Travis CI

* Some clear names for workflow and steps

* Add cache to bin compat step

* Also run MiMa for master branch and tags

* Use JDK 8 to validate pull request

* Move validateCompile to pull request validation

Also remove `update` and `Test/compile` from binary compatibility checks:

- `validateCompile` runs for all configurations, so it overrides `Test/compile`
- `update` is unnecessary for mima checks
2021-08-23 11:02:17 +02:00

37 lines
1.1 KiB
YAML

name: Binary Compatibility
on:
pull_request:
push:
branches:
- master
tags:
- v2.6.*
jobs:
check-binary-compatibility:
name: Check / Binary Compatibility
runs-on: ubuntu-20.04
strategy:
matrix:
# The versions of scala specified here are only used as `-Dakka.build.scalaVersion=...`
# which ignores the PATCH portion of the version id. These Scala versions don't need
# to be fully defined here then since Akka build handles which patch version will be used.
scalaVersion: [ "2.12", "2.13" ]
steps:
- name: Checkout
uses: actions/checkout@v2
with:
# we don't know what commit the last tag was it's safer to get entire repo so previousStableVersion resolves
fetch-depth: 0
- name: Set up JDK 8
uses: olafurpg/setup-scala@v10
with:
java-version: adopt@1.8.0
- name: Cache Coursier cache
uses: coursier/cache-action@v6.2
- name: Report MiMa Binary Issues
run: sbt -jvm-opts .jvmopts-ci -Dakka.build.scalaVersion=${{ matrix.scalaVersion }} mimaReportBinaryIssues