[donat]

Description

Publishes a Develocity Build Scan for each image the Unit Tests workflow builds. The Gradle builds already publish Build Scans to develocity.apache.org. With this change the image builds do too, showing the duration and cache use of each Dockerfile step, the build log and the packages in each image.

A new Setup Docker step runs the Develocity Docker build agent beside the build, using the setup-docker action from gradle/develocity-actions. The agent captures what reaches BuildKit, so the Dockerfiles and the build commands stay as they are.

The scans go to develocity.apache.org under the openwhisk project, with the DEVELOCITY_ACCESS_KEY secret the Gradle builds already use. Pull request runs from forks have no access key, so they build the images as before and publish no scan.

Tested on a mirror of this repository, where the Unit Tests workflow published a Build Scan for each of the 12 images it builds.

Documentation for the action: https://github.com/gradle/develocity-actions#setup-docker-action

The pinned version of the action is on the ASF actions allowlist: apache/infrastructure-actions#1364

Related issue and scope

• I opened an issue to propose and discuss this change (#????)

My changes affect the following components

• API
• Controller
• Message Bus (e.g., Kafka)
• Loadbalancer
• Scheduler
• Invoker
• Intrinsic actions (e.g., sequences, conductors)
• Data stores (e.g., CouchDB)
• Tests
• Deployment
• CLI
• General tooling
• Documentation

Types of changes

• Bug fix (generally a non-breaking change which closes an issue).
• Enhancement or new feature (adds new functionality).
• Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

• I signed an Apache CLA.
• I reviewed the style guides and followed the recommendations (Travis CI will check :).
• I added tests to cover my changes.
• My changes require further changes to the documentation.
• I updated the documentation where necessary.