Add a few more GitHub actions to replace some CircleCI #263
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following the discussion with @paulk-asert, I started going through the remaining actions on CircleCI to see about moving them over to GitHub Actions or Jenkins.
This removes the easy-to-reach ones. The remaining few will require some secrets management, as they require API keys to BrowserStack, SauceLabs, or LambdaTest.
I've got access to those via the Geb org that Marcin shared with me when handing things over.
Maintaining Geb's integration with those providers will require setting those up as shared secrets. I don't appear to have access to do that in GitHub like I did for the geb organization (https://github.com/organizations/geb/settings/secrets/actions).
I could probably get that done with a request to Apache Infra, for either GH Actions or Jenkins. If we do that, we can completely remove the CircleCI build.
I went ahead and used the build cache on the new files. I'm trusting that the Gradle tasks are deterministic enough that we needn't re-run them (see, e.g. https://blog.gradle.org/stop-rerunning-tests).