Skip to content

feat: Add shared-bucket multitenancy support for OSS attachments #232

feat: Add shared-bucket multitenancy support for OSS attachments

feat: Add shared-bucket multitenancy support for OSS attachments #232

Triggered via pull request April 1, 2026 12:12
@SchmarviniusSchmarvinius
synchronize #767
Status Success
Total duration 14m 38s
Artifacts 2

pr.yml

on: pull_request_target
Waiting for PR approval as this workflow runs on pull_request_target
Waiting for PR approval as this workflow runs on pull_request_target
Matrix: build-and-test / build
Matrix: build-and-test / integration-tests
build-and-test  /  CodeQL Analysis
2m 31s
build-and-test / CodeQL Analysis
build-and-test  /  SonarQube Scan
3m 6s
build-and-test / SonarQube Scan
build-and-test  /  Deploy snapshot to Artifactory
0s
build-and-test / Deploy snapshot to Artifactory
Fit to window
Zoom out
Zoom in

Annotations

20 errors and 41 warnings
build-and-test / Build (Java 17)
2026-04-01 12:14:28,371 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.Items.attachments') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [5dc91c5a-b96f-4218-8384-d732f1a82b32]
build-and-test / Build (Java 17)
2026-04-01 12:14:27,556 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.Items.attachments') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [1acb0d89-97e2-4c5a-b79c-c474d95f90d0]
build-and-test / Build (Java 17)
2026-04-01 12:14:27,374 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.AttachmentEntity') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [bf53624a-8584-432f-b8dc-d8b7c63be14c]
build-and-test / Build (Java 17)
2026-04-01 12:14:27,363 ERROR [ForkJoinPool.commonPool-worker-1] []: Error scanning attachment e3ad57df-0f3d-4db7-ba21-ececc1982133 in entity TestService.AttachmentEntity. [com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner] []
build-and-test / Build (Java 17)
12:13:19.644 [main] ERROR com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner -- Error scanning attachment 68e71fb4-a52d-415e-b987-19fc7e49be4a in entity null.
build-and-test / Build (Java 17)
12:13:19.538 [ForkJoinPool.commonPool-worker-1] ERROR com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner -- Error scanning attachment 1bc6edc5-8cf9-4436-aae2-663298dc29bf in entity null.
build-and-test / Build (Java 17)
12:13:16.629 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
build-and-test / Build (Java 17)
12:13:16.627 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
build-and-test / Build (Java 17)
12:13:16.449 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
build-and-test / Build (Java 17)
12:13:16.409 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
build-and-test / Build (Java 21)
2026-04-01 12:14:41,511 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.AttachmentEntity') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [fdcd0a5f-4b89-4189-a088-c39215201ddc]
build-and-test / Build (Java 21)
2026-04-01 12:14:39,818 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.Items.attachments') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [44860fdd-2935-4ec3-a6e3-71dfb5a88abf]
build-and-test / Build (Java 21)
2026-04-01 12:14:38,975 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.Items.attachments') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [75392bd3-7ea9-4e34-8d71-e31c7776da42]
build-and-test / Build (Java 21)
2026-04-01 12:14:38,778 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.AttachmentEntity') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [b003df31-2225-427a-92d5-076f0b1183c4]
build-and-test / Build (Java 21)
12:13:25.865 [ForkJoinPool.commonPool-worker-2] ERROR com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner -- Error scanning attachment ad9509f9-c136-4daf-a074-d4e581877faf in entity null.
build-and-test / Build (Java 21)
12:13:25.760 [ForkJoinPool.commonPool-worker-2] ERROR com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner -- Error scanning attachment eeebac18-07b3-4255-98a0-78391235fedf in entity null.
build-and-test / Build (Java 21)
12:13:22.720 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
build-and-test / Build (Java 21)
12:13:22.718 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
build-and-test / Build (Java 21)
12:13:22.547 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
build-and-test / Build (Java 21)
12:13:22.521 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
build-and-test / Build (Java 17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SAP/project-piper-action@main, stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-test / Build (Java 17)
12:13:17.097 [main] WARN com.sap.cds.feature.attachments.service.malware.client.DefaultMalwareScanClient -- Document is infected with malware, response status from scan was: malwareDetected = true, encryptedContentDetected = false
build-and-test / Build (Java 17)
12:13:16.687 [main] WARN com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- More than one attachment found in entity unit.test.Attachment.
build-and-test / Build (Java 17)
[WARNING]
build-and-test / Build (Java 17)
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
build-and-test / Build (Java 17)
[WARNING]
build-and-test / Build (Java 17)
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
build-and-test / Build (Java 17)
[WARNING]
build-and-test / Build (Java 17)
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-resources-plugin is missing. @ com.sap.cds.integration-tests:cds-feature-attachments-integration-tests-mtx-local:${revision}, /home/runner/work/cds-feature-attachments/cds-feature-attachments/integration-tests/mtx-local/srv/pom.xml, line 199, column 15
build-and-test / Build (Java 17)
[WARNING] Some problems were encountered while building the effective model for com.sap.cds.integration-tests:cds-feature-attachments-integration-tests-mtx-local:jar:1.4.0-SNAPSHOT
build-and-test / Build (Java 17)
[WARNING]
build-and-test / Build (Java 21)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SAP/project-piper-action@main, stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-test / Build (Java 21)
WARNING: If a serviceability tool is in use, please run with -XX:+EnableDynamicAgentLoading to hide this warning
build-and-test / Build (Java 21)
WARNING: A Java agent has been loaded dynamically (/home/runner/.m2/repository/net/bytebuddy/byte-buddy-agent/1.17.7/byte-buddy-agent-1.17.7.jar)
build-and-test / Build (Java 21)
[WARNING]
build-and-test / Build (Java 21)
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
build-and-test / Build (Java 21)
[WARNING]
build-and-test / Build (Java 21)
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
build-and-test / Build (Java 21)
[WARNING]
build-and-test / Build (Java 21)
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-resources-plugin is missing. @ com.sap.cds.integration-tests:cds-feature-attachments-integration-tests-mtx-local:${revision}, /home/runner/work/cds-feature-attachments/cds-feature-attachments/integration-tests/mtx-local/srv/pom.xml, line 199, column 15
build-and-test / Build (Java 21)
[WARNING] Some problems were encountered while building the effective model for com.sap.cds.integration-tests:cds-feature-attachments-integration-tests-mtx-local:jar:1.4.0-SNAPSHOT
build-and-test / Build (Java 21)
[WARNING]
build-and-test / CodeQL Analysis
Starting April 2026, the CodeQL Action will skip computing file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. To opt out of this change, set the `CODEQL_ACTION_FILE_COVERAGE_ON_PRS` environment variable to `true`. Alternatively, create a custom repository property with the name `github-codeql-file-coverage-on-prs` and the type "True/false", then set this property to `true` in the repository's settings.
build-and-test / CodeQL Analysis
Cannot build an overlay database because build-mode is set to "manual" instead of "none". Falling back to creating a normal full database instead.
build-and-test / SonarQube Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SAP/project-piper-action@main, stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-test / SonarQube Scan
12:24:30.989 WARN Invalid character encountered in file /home/runner/work/cds-feature-attachments/cds-feature-attachments/doc/img/Restore_Documents.png at line 1 for encoding UTF-8. Please fix file content or configure the encoding to be used using property 'sonar.sourceEncoding'.
build-and-test / SonarQube Scan
12:24:30.963 WARN Invalid character encountered in file /home/runner/work/cds-feature-attachments/cds-feature-attachments/doc/img/Delete_Success.vsdx at line 1 for encoding UTF-8. Please fix file content or configure the encoding to be used using property 'sonar.sourceEncoding'.
build-and-test / SonarQube Scan
12:24:30.960 WARN Invalid character encountered in file /home/runner/work/cds-feature-attachments/cds-feature-attachments/doc/img/Create_Success.png at line 1 for encoding UTF-8. Please fix file content or configure the encoding to be used using property 'sonar.sourceEncoding'.
build-and-test / SonarQube Scan
12:24:30.946 WARN Invalid character encountered in file /home/runner/work/cds-feature-attachments/cds-feature-attachments/doc/img/Read_wrong_status.vsdx at line 1 for encoding UTF-8. Please fix file content or configure the encoding to be used using property 'sonar.sourceEncoding'.
build-and-test / SonarQube Scan
12:24:30.923 WARN Invalid character encountered in file /home/runner/work/cds-feature-attachments/cds-feature-attachments/doc/img/Delete_Success.png at line 1 for encoding UTF-8. Please fix file content or configure the encoding to be used using property 'sonar.sourceEncoding'.
build-and-test / SonarQube Scan
12:24:30.764 WARN Use of preview features have been detected during analysis. Enable DEBUG mode to see them.
build-and-test / SonarQube Scan
12:24:30.763 WARN Unresolved imports/types have been detected during analysis. Enable DEBUG mode to see them.
build-and-test / SonarQube Scan
12:24:30.759 WARN Dependencies/libraries were not provided for analysis of SOURCE files. The 'sonar.java.libraries' property is empty. Verify your configuration, as you might end up with less precise results.
build-and-test / SonarQube Scan
12:24:22.373 WARN Could not find ref 'main' in refs/heads, refs/remotes, refs/remotes/upstream or refs/remotes/origin
build-and-test / SonarQube Scan
12:24:06.707 WARN File '/home/runner/work/cds-feature-attachments/cds-feature-attachments/v1_501_0/piper' is bigger than 20MB and as consequence is removed from the analysis scope.
build-and-test / Integration Tests (Java 17, latest-version)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-test / Integration Tests (Java 17, build-version)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-test / Integration Tests (Java 21, build-version)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-test / Integration Tests (Java 21, latest-version)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-test / Integration Tests (Java 21, oss)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-test / Integration Tests (Java 17, oss)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
build-artifacts-java-17 Expired
1.14 MB
sha256:8a9c200ee45acbecb1fc3520b8290d867b792f6a65218b94527a52c50715c5af
build-artifacts-java-21 Expired
1.18 MB
sha256:dae8166bacfaf7b3af70e2776cbaccaa631bf794fb92591ace8526e3ba38b180