-
Story
-
Resolution: Unresolved
-
Major
-
Ongoing Prod
-
False
-
None
-
False
-
---
-
-
Story: As a productization engineer, I need to know which artifacts were added in the current compose compared to the previous build, so that unexpected diversions get detected before handover to QE.
Proposal:
As discussed in https://issues.redhat.com/browse/QUARKUS-4895?focusedId=25525903&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-25525903, for a starter productization team could look into these two job definitions QE uses:
- https://gitlab.cee.redhat.com/quarkus-qe/jenkins-jobs/-/blob/main/jobs/utils/quarkus_maven_repo_gav_diff.groovy
- compares 2 maven repo zips
- https://gitlab.cee.redhat.com/quarkus-qe/jenkins-jobs/-/blob/main/jobs/utils/quarkus_artiffact_version_diff_upstream_rhbq.groovy
- compares productized and community platform BOM, uses https://github.com/quarkus-qe/quarkus-utilities/tree/main/artifact-version-diff
Example jobs:
- https://main-jenkins-csb-quarkusqe.apps.ocp-c1.prod.psi.redhat.com/job/rhbq-platform-quarkus-maven-repo-gav-diff/
- https://main-jenkins-csb-quarkusqe.apps.ocp-c1.prod.psi.redhat.com/job/utils-compare-artifacts-upstream-vs-prod/
Use these resources for inspiration or adopt them in productization pipeline as you want.