[Infra] Add explicit call to revapi github action to ensure it's not skipped

[kbendick]

The revapi action is sometimes skipping.

This is possibly due to the cache (in which case we'd need to be more explicit about which dependencies are cached).

We can either try this or ./gradlew clean :iceberg-api:build -x test -x integrationTest -x javadoc to try it out. I'm open to either.

I'll look into the revapi action upstream to see if there's a better way we can force it or if they have any guidance. This worked locally for me though as clean should force iceberg-api:revapi to invoke build.

cc @singhpk234 @ajantha-bhat

[kbendick]

I think we can also mark this as not up to date, or run this particular action without clean, but with --rerun-tasks.

See https://stackoverflow.com/questions/42175235/force-gradle-to-run-task-even-if-it-is-up-to-date

[ajantha-bhat]

can we also do some dummy changes in the api/ module (until the review is done)? So, it will run the rev api check? Now out of 26 checks it ran, I don't see the rev api check.

[findepi]

is :iceberg-api:revapi success cached from earlier runs?

[kbendick]

No, not entirely.

The problem, as outlined in the new PR #4989, was that the actions/checkout github action uses a depth of 1 by default.

So the "head" (master) branch is in a detached state, and thus the tags needed for the action to work (basically the output of git describe) was failing.

I did remove the cache, which then caused the tests to at least run revapi. But they still passed because the plugin couldn't properly determine the old version (via the tag) and then the new version via the override in the .palantir/revapi.yaml file).

Let's continue the discussion in #4989

[kbendick]

Replaced by #4989