donat opened a new pull request, #11759: URL: https://github.com/apache/nifi/pull/11759
<!-- Licensed to the Apache Software Foundation (ASF) under one or more --> <!-- contributor license agreements. See the NOTICE file distributed with --> <!-- this work for additional information regarding copyright ownership. --> <!-- The ASF licenses this file to You under the Apache License, Version 2.0 --> <!-- (the "License"); you may not use this file except in compliance with --> <!-- the License. You may obtain a copy of the License at --> <!-- http://www.apache.org/licenses/LICENSE-2.0 --> <!-- Unless required by applicable law or agreed to in writing, software --> <!-- distributed under the License is distributed on an "AS IS" BASIS, --> <!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. --> <!-- See the License for the specific language governing permissions and --> <!-- limitations under the License. --> # Summary [NIFI-00000](https://issues.apache.org/jira/browse/NIFI-00000) Publishes a Develocity Build Scan for each container image the `docker-tests` workflow builds. 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 builds that reach BuildKit. docker-maven-plugin uses BuildKit only when a platform is named, and the Docker Engine API otherwise. The four image modules therefore build with `buildx` on the `default` builder, for the new `docker.build.platform` property: `linux/amd64`, or `linux/arm64` on arm64 hosts through the `docker-platform-arm64` profile. The scans go to develocity.apache.org under the `nifi` project, with the `NIFI_DEVELOCITY_ACCESS_KEY` secret the Maven builds already use. Documentation for the action: https://github.com/gradle/develocity-actions#setup-docker-action `gradle/develocity-actions/setup-docker` is not on the ASF actions allowlist yet. It has to be added in https://github.com/apache/infrastructure-actions before this workflow can run it. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000` - Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000` - Pull request contains [commits signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) with a registered key indicating `Verified` status ### Pull Request Formatting - Pull Request based on current revision of the `main` branch - Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `./mvnw clean install -P contrib-check` - [ ] JDK 21 - [ ] JDK 25 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
