Idea #22858
closed
Make it possible to run build-packages-* without uploading packages
Description
Problem: If you're making changes to package building (the stuff under build/), basically the only way you can test those is by running the build-packages-* Jenkins jobs.
However, those jobs also upload packages. If you build packages out of a branch, you can create situations where tordo doesn't get code changes it should, because packages built from main might have an "older" version timestamp than packages built out of your branch that branched off before the code changes.
Solution: I guess we implement a checkbox, default checked, that determines whether or not we pass the --upload option to our package build script, and you uncheck it when you're doing testing. The ergonomics of that aren't great but it maintains backwards compatibility and this is rare enough personally I can live with the papercut.
Updated by Peter Amstutz
Updated by Brett Smith 11 months ago
Peter Amstutz wrote in #note-1:
This sounds like a good idea to me, if this is blocking you for testing Rocky 9 I'd say go ahead and do it.
It is not a blocker, but it is part of the reason 21362-rhel9-packages caused package build failures. See #21362#note-12 - I tested Docker image changes on Debian 12, but not other distributions, because testing all distributions locally would've taken a ton of time and I didn't want to test on Jenkins because of the tordo problem discussed here. If I could've suppressed uploads, I would've run the Jenkins job and found the build failures before merge.
Updated by Brett Smith 9 months ago
- Assigned To set to Brett Smith
- Status changed from New to In Progress