Improve speed and reliability of repo management #157
Conversation
Updated infrastructure-repository-update.yml to use the new 3-step parallel repository architecture that eliminates duplicate work. Workflow changes: - Step 1: main job builds common component with update-main - Step 2: postclean jobs build release-specific components in parallel using -R flag (isolated DBs, no publishing) - Step 3: NEW merge job combines common + release-specific components and publishes complete repositories - Updated cleanup job dependency to wait for merge Benefits: - Common packages added once instead of per-release - True parallelism across multiple releases - Better error isolation between releases - Scalable architecture for adding more releases Signed-off-by: Igor Pecovnik <[email protected]>
This reverts commit 7f06a08.
- Replace DOWNLOAD_PATH with UPLOAD_PATH environment variable
- Update UPLOAD_PATH to "storage/incoming/external" for better organization
- Update all rsync commands to use ${UPLOAD_PATH} instead of hardcoded "storage/"
- Add example.deb to each generated subfolder (main, utils, desktop) to ensure
empty repos are properly published with complete structure
This ensures repository components are always publishable even when no
packages are added to them.
Signed-off-by: Igor Pecovnik <[email protected]>
Add architecture-aware filtering when checking for existing packages on remote storage to prevent skipping downloads for wrong architectures. - Map Debian arch names to common filename variants (amd64→x86_64,x64, arm64→aarch64, etc.) - Build find command with architecture-specific patterns - Only skip download if package exists for matching architecture Signed-off-by: Igor Pecovnik <[email protected]>
|
Warning Rate limit exceeded@igorpecovnik has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 6 minutes and 59 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (2)
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Note: this will still use temp branch at build repo armbian/build#9230