PI 12 Iteration 3

[RazvanZmau]

GOAL: Data Sovereignty

Role rotation:

• @ds-mmaul responsible for release
• @ds-lcapellino firefighter & DevOps meeting participant
• @ds-mwesener / @ds-ext-sceronik rotating docu guru / security minister
• @ds-alexander-bulgakov & @mkanal test management

Minister Security

@ds-mwesener
Timebox: 2h

• Trivy shows no high or critical findings in github security tools tab. Pipeline runs successful
  -> Created ticket: Fix code scanning alert - spring-security: Broken Access Control in Spring Security With Direct Use of isFullyAuthenticated #709
• Kics shows no high or critical findings in github security tools tab. Pipeline runs successful
• Dashtool on Tractus-X checked? Release Manager has been informed about rejected licenses.
• Security Tab Issues reduced by 10 until it is by 0
• There are no Security Bumps on Tractus-X left. Everything has been either merged, mitigated or story created.
• Created issue: Dependency updates (Spring Boot, Spring Cloud, Spring Core) #718
• Invicti tool has been executed on the latest catena release. There are no high / critical findings.
• Dependency Check has been executed and high / critical dependencies have been updated / mitigated / story created.
  mvn --batch-mode clean package dependency-check:aggregate -pl tx-models,tx-backend -Pdependency-check -DskipTests
• All of the catena pipelines run green on main
• Reviewed by the team and approved (Last Friday Sprint-Daily of the current sprint.)

Release Champion:

@ds-mmaul
Timebox: 2h

• Trace-X Release created for catena
• Helm-Chart Release created for catena
• Release created for tractus-x
• Helm-Chart Release created for tractus-x
• Deployed release on int-a
• Deployed release on int-b
• Verified the release on int-a and int-b is ready for Sprint Review
• Reviewed by the team and approved
• Update COMPATIBILITY_MATRIX
  --> Releases are done. INT not deployed since somehow the release branch is not existing for argo

Docu-Guru:

@ds-ext-sceronik
Timebox: 2h

• Confluence Documentation has been updated
• GitHub Documentation has been updated
• At least 1 TODO-Comment has been added in the source code to reflect technical dept
• New colleague on board - added to authors.md, team calendar updated
• Implemented concepts have been moved to the archive
• Identify doc which is not used and add a comment / address it for removal
• Reviewed by the team and approved
• Check the Improvements of the Trace-X documentation #655 discussion
• Request feedback about documentation in the matrix chat.

Testmanager

@ds-alexander-bulgakov
@mkanal

• Update Release 24.03 ---- Content Overview
• Update Test Status - PI12 Test Status - PI12
• Update Integration Test - PI12 - Release 2024.05

Firefighter

@ds-lcapellino

• Maintenance of our community in Matrix Chat https://matrix.to/#/#tractusx-trace-x:matrix.eclipse.org
• Response to Github issues https://github.com/eclipse-tractusx/traceability-foss/issues
• To be defined, eg: Onboarding of new colleague, quality-gates, escalation topics
• Communicating and discussing with external contributors in Eclipse Matrix Chat

[ds-alexander-bulgakov]

• Update Test Status - PI12