[25/03][TRACE-X] Release Checks

[mkanal]

Release Info

Please provide information on what you want to be included in the Eclipse Tractus-X release.
If you are not owner of this issue, please provide the information as comment to the issue.
Make sure to assign this issue to expert(s) for their approval, as soon as you have finished preparation. Multiple assignees allowed; they will un-assign themselves once review completed.

Responsible contacts:

• Committer: @mkanal
• ExpertGroup: GitHub handle IC - Committee
• Contributor contact: @mkanal

Version to be included in Eclipse Tractus-X release:

• App version: 14.0.1
• Helm Chart version: 1.4.1

Leading product repository: traceability-foss

Compliance

IC - Committee
@eckardg
@JSterthues
@Grand-Thibault

• Possible changes (through the new features) on related Catena-X standards are considered and addressed
• Tractus-X Release Guidelines(TRGs) fulfilled
  • QG Checks (Release 25.03) traceability-foss#1388

Make sure to open and fill in a separate documentation issue in your product repository using the Quality Gate Checklist issue template

Note

Note: most criteria for documentation and security are now covered in TRGs

Functionality

• Feature works as expected and described
• Backward compatibility maintained (depending Major/ Minor)

Performance

• Memory and CPU usage is within acceptable limits oriented with goldilocks

Testing

• Unit tests cover all new features
• Integration tests are updated
• E2E/Integration test passed
• Regressions tests passed

Feature summary

Please provide a list of all features that have been developed in the current phase. This list is essential for several reasons:

• Test Preparation: Identifying new features will help in the creation of new end-to-end (E2E) tests and ensure that the relevant aspects are thoroughly tested.
• Awareness: It will raise awareness of the features that need to be prioritized during the testing process.
• Board Management: This will assist in keeping the project board organized and up-to-date.

By documenting these features, you will contribute to a smoother and more efficient release process.

Note

Note: all features needs to be closed to get approval for release

Testplan

[25.03] Trace-X FOSS E2E-Testplan

Feature	Test Status	Note
🌟🆙🚀Trace-X Data Provisioning used digitalTwinType for register assets in dtr #940	🟢 Tested successfully	Only minor changes and bugfixes - Unit, integration and automated e2e tests executed successfully in upstream Test run
🌟🆙🚀API Key of Consumer EDC is also used for Provider EDC #890	🟢 Tested successfully	Only minor changes and bugfixes - Unit, integration and automated e2e tests executed successfully in upstream Test run
🌟🆙🚀Introduce environment variable for cron expression of AssetRefreshJob #932	🟢 Tested successfully	Only minor changes and bugfixes - Unit, integration and automated e2e tests executed successfully in upstream Test run
🌟🆙🚀Several scalability improvements #1386	🟢 Tested successfully	Only minor changes and bugfixes - Unit, integration and automated e2e tests executed successfully in upstream Test run

Release Documentation

• Release notes/Changelogs are updated
• Migration scripts/documentation are included if necessary (Ensure that any database or infrastructure migrations are included).
• Known knowns
  • topic 1
  • topic 2

Summary

Please provide a short summary about the new values/benefits of the new features here:

• [TRACE-X] 🌟🚀Trace-X Data Provisioning used digitalTwinType for register assets the dtr #940 ➡️ Introducing the "digitalTwinType" specialAssetId ensures that the Trace-X application is fully compatible with IndustryCore 2.0.0 standards, promoting better interoperability and streamlined data management for digital twins. This upgrade will make the system more aligned with the latest industry guidelines, improving its ability to participate in broader data ecosystems.
• ❓[TRACE-X] API Key of Consumer EDC is also used for Provider EDC item-relationship-service#890 ➡️ Previously, Trace-X was using the same API Key to authenticate against the consumer and provider EDC. This is now fixed by adding a dedicated configuration property for consumer and provider API Key
• [TRACE-X] 🌟🚀Introduce environment variable for cron expression of AssetRefreshJob #932 ➡️ The cron interval in which the AssetRefreshJob is executed was a hardcoded property and can now be configured.
• Scalabality improvements traceability-foss#1386 ➡️ This feature includes miscellaneous changes to the internal processing of Trace-X. This includes enhancements of API functionality: cascading removal for asset entities, API key authentication for quality notifications, and a backend API for search filtering, and a switch to the IRS Order API

Helpful Links

• Eclipse Tractus-X API Hub

[mkanal]

[ ] @ds-mwesener please add the last version once you have released the upstream and all e2e exceuted successfully.
App version: 14.0.0
Helm Chart version: 1.4.0

fyi @rogocof

[ds-lcapellino]

Resource requests have been adjusted to Goldilocks recommendations:
https://goldilocks.int.catena-x.net/dashboard/product-traceability-foss
https://grafana.int.catena-x.net/d/cdtljo1hajev4a/int-cluster?orgId=1

[ther3sa]

QG-Review 26-02-2025

Has been checked

• Responsible contacts listed ✔️
• Version listed ✔️
• Possible changes on related Catena-X standards are considered and addressed ✔️
• TRG check is done ✔️
• Functionality checked ✔️
• Performance checked ✔️
• Testing is done ✔️
• Release Documentation ✔️

[ther3sa]

QG Approval

Congrats! 🎉
Quality Gate fully approved with all necessary pre-requisites fulfilled!

Thanks for all your efforts!!

[ds-mwesener]

Thank you @ther3sa I have just updated the latest release versions in the description of the issue:

Version to be included in Eclipse Tractus-X release:

App version: 14.0.1
Helm Chart version: 1.4.1

[ther3sa]

Thank you @ther3sa I have just updated the latest release versions in the description of the issue:

Version to be included in Eclipse Tractus-X release:

App version: 14.0.1 Helm Chart version: 1.4.1

Thanks I have adapted the versions in the summary check and in the future changelog