Update version to 1.3.3 #44
main.yml
on: push
Matrix: build-and-test / build
Blackduck Scan
1m 12s
Matrix: build-and-test / integration-tests
build-and-test
/
SonarQube Scan
3m 3s
build-and-test
/
Deploy snapshot to Artifactory
14s
Annotations
20 errors and 42 warnings
|
build-and-test / Build (Java 17)
2026-03-15 19:08:06,823 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestDraftService.AttachmentEntity_drafts') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [c6cdb920-85e4-4536-8762-df676a51bfa4]
|
|
build-and-test / Build (Java 17)
2026-03-15 19:08:06,789 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestDraftService.Items.attachments_drafts') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [7bbc317e-f692-41dc-8b77-f73dfd80edc7]
|
|
build-and-test / Build (Java 17)
2026-03-15 19:08:06,348 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestDraftService.AttachmentEntity_drafts') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [6ce994d3-989b-41da-adc6-c5e45d9d6378]
|
|
build-and-test / Build (Java 17)
2026-03-15 19:08:06,293 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestDraftService.Items.attachments_drafts') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [c3a96250-c892-4012-ac03-45f8d6668d30]
|
|
build-and-test / Build (Java 17)
19:07:02.495 [ForkJoinPool.commonPool-worker-2] ERROR com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner -- Error scanning attachment 37c4a8ec-855c-4872-b484-574c53fa405e in entity null.
|
|
build-and-test / Build (Java 17)
19:07:02.384 [ForkJoinPool.commonPool-worker-2] ERROR com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner -- Error scanning attachment 1daa2729-2ab0-4ca1-a197-783c6f5e9950 in entity null.
|
|
build-and-test / Build (Java 17)
19:07:01.872 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
|
|
build-and-test / Build (Java 17)
19:07:01.870 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
|
|
build-and-test / Build (Java 17)
19:07:01.774 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
|
|
build-and-test / Build (Java 17)
19:07:01.758 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
|
|
build-and-test / Build (Java 21)
2026-03-15 19:08:07,606 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestDraftService.AttachmentEntity_drafts') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [38aad66e-205a-430e-8172-ba9bc8b6ed7a]
|
|
build-and-test / Build (Java 21)
2026-03-15 19:08:07,571 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestDraftService.Items.attachments_drafts') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [a31fea62-0152-4b3f-a54d-f528640c17cc]
|
|
build-and-test / Build (Java 21)
2026-03-15 19:08:07,119 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestDraftService.AttachmentEntity_drafts') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [df7d2c31-d096-4f7b-a902-358ca9362bd0]
|
|
build-and-test / Build (Java 21)
2026-03-15 19:08:07,048 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestDraftService.Items.attachments_drafts') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [d3a778a5-9f73-4dae-81c2-55bcd4f48b47]
|
|
build-and-test / Build (Java 21)
19:07:03.597 [ForkJoinPool.commonPool-worker-1] ERROR com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner -- Error scanning attachment 98f7838f-56ab-46b4-8717-ffd999554136 in entity null.
|
|
build-and-test / Build (Java 21)
19:07:03.488 [ForkJoinPool.commonPool-worker-1] ERROR com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner -- Error scanning attachment 704f295e-f452-4343-9921-da1d7199ffda in entity null.
|
|
build-and-test / Build (Java 21)
19:07:02.943 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
|
|
build-and-test / Build (Java 21)
19:07:02.942 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
|
|
build-and-test / Build (Java 21)
19:07:02.852 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
|
|
build-and-test / Build (Java 21)
19:07:02.834 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
|
|
Blackduck 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. 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)
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. 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)
19:07:58,674 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.sap.cds.services.impl.runtime.CdsRuntimeImpl] to WARN
|
|
build-and-test / Build (Java 17)
19:07:58,674 |-INFO in ch.qos.logback.core.model.processor.ModelInterpretationContext@4bb8855f - value "WARN" substituted for "${LOG_CDS_RUNTIME_IMPL_LEVEL:-WARN}"
|
|
build-and-test / Build (Java 17)
[WARNING] JAR will be empty - no content was marked for inclusion!
|
|
build-and-test / Build (Java 17)
[WARNING] No files to analyze. Check input paths and exclude parameters, use --debug to see file collection traces.
|
|
build-and-test / Build (Java 17)
[WARNING] No files to analyze. Check input paths and exclude parameters, use --debug to see file collection traces.
|
|
build-and-test / Build (Java 17)
19:07:05.695 [main] WARN com.sap.cds.feature.attachments.configuration.Registration -- OutboxService 'DefaultOutboxUnordered' is not available. AttachmentService will not be outboxed.
|
|
build-and-test / Build (Java 17)
19:07:01.894 [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)
19:07:00.168 [main] WARN com.sap.cds.feature.attachments.service.malware.client.DefaultMalwareScanClient -- Document is infected with malware, response status from scan was: malwareDetected = true, encryptedContentDetected = true
|
|
build-and-test / Build (Java 17)
19:07:00.159 [main] WARN com.sap.cds.feature.attachments.service.malware.client.DefaultMalwareScanClient -- Document is infected with malware, response status from scan was: malwareDetected = false, encryptedContentDetected = true
|
|
build-and-test / Build (Java 17)
19:07:00.143 [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 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. 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: 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)
19:07:06.945 [main] WARN com.sap.cds.feature.attachments.configuration.Registration -- OutboxService 'DefaultOutboxUnordered' is not available. AttachmentService will not be outboxed.
|
|
build-and-test / Build (Java 21)
19:07:02.966 [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 21)
19:07:01.299 [main] WARN com.sap.cds.feature.attachments.service.malware.client.DefaultMalwareScanClient -- Document is infected with malware, response status from scan was: malwareDetected = true, encryptedContentDetected = true
|
|
build-and-test / Build (Java 21)
19:07:01.289 [main] WARN com.sap.cds.feature.attachments.service.malware.client.DefaultMalwareScanClient -- Document is infected with malware, response status from scan was: malwareDetected = false, encryptedContentDetected = true
|
|
build-and-test / Build (Java 21)
19:07:01.277 [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 21)
WARNING: Dynamic loading of agents will be disallowed by default in a future release
|
|
build-and-test / Build (Java 21)
WARNING: If a serviceability tool is not in use, please run with -Djdk.instrument.traceUsage for more information
|
|
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 / CodeQL Analysis
Cannot build an overlay-base 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. 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
19:15:48.448 WARN * cds-feature-attachments/src/test/java/com/sap/cds/feature/attachments/configuration/RegistrationTest.java
|
|
build-and-test / SonarQube Scan
19:15:48.446 WARN * cds-feature-attachments/src/main/java/com/sap/cds/feature/attachments/handler/draftservice/DraftPatchAttachmentsHandler.java
|
|
build-and-test / SonarQube Scan
19:15:48.446 WARN * cds-feature-attachments/src/test/java/com/sap/cds/feature/attachments/service/handler/AttachmentsServiceImplHandlerTest.java
|
|
build-and-test / SonarQube Scan
19:15:48.440 WARN Missing blame information for the following files:
|
|
build-and-test / SonarQube Scan
19:15:48.437 WARN Shallow clone detected, no blame information will be provided. You can convert to non-shallow with 'git fetch --unshallow'.
|
|
build-and-test / SonarQube Scan
19:15:44.933 WARN Retrieving only language associated files, make sure to run the analysis inside a git repository to make use of inclusions specified via "sonar.text.inclusions"
|
|
build-and-test / SonarQube Scan
19:15:42.065 WARN Use of preview features have been detected during analysis. Enable DEBUG mode to see them.
|
|
build-and-test / SonarQube Scan
19:15:42.065 WARN Unresolved imports/types have been detected during analysis. Enable DEBUG mode to see them.
|
|
build-and-test / SonarQube Scan
19:15:42.060 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
19:15:24.425 WARN File '/home/runner/work/cds-feature-attachments/cds-feature-attachments/v1_497_0/piper' is bigger than 20MB and as consequence is removed from the analysis scope.
|
|
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. 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. 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. 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, 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. 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. 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. 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 / Deploy snapshot to Artifactory
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. 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
|
1010 KB |
sha256:79924c5826b17f7443a57243875cbdb4efc2b20ce35178a3fd35eca8a8c7fcc6
|
|
|
build-artifacts-java-21
Expired
|
1.03 MB |
sha256:ce054b9ddc7e41b5283a477faa55232bdf4e62ae24f0600eb4a023d611d25fe1
|
|