Open
Description
Two invocations of krel obs specs command with the same parameters are going to provide different tarballs (i.e. with tarballs with different hashes). If we would push these tarballs to OBS, it would trigger the build process two times with different package revisions, even though it's building the same package and version.
OBS can detect this and avoid running the build process the second time if tarballs are identical (i.e. hashes are identical), but as that's not the case for us, it would trigger the build process two times. We should look into feasibility of having reproducible krel obs specs specs and tarballs to avoid this.
/sig release
/area release-eng
/kind feature
/priority important-longterm
Metadata
Metadata
Assignees
Labels
Issues or PRs related to the Release Engineering subprojectCategorizes issue or PR as related to a new feature.Indicates that an issue or PR should not be auto-closed due to staleness.Important over the long term, but may not be staffed and/or may need multiple releases to complete.Categorizes an issue or PR as relevant to SIG Release.
Type
Projects
Status
🔖 Backlog