chaotic-cx / chaotic-repository-template Goto Github PK

Some packages have very large source downloads. Caching sources would save significant bandwidth on rebuilds.

Example packages include chromium-based browsers, firefox-based browsers, and many -git packages.

Instead of entirely clearing cache, problem files could be deleted:

• When the hash changes. Check .SRCINFO
• The git repo is out of sync. Compare .SRCINFO with .git/config

Full cache clear could be triggered manually. Since each builder may have its own cache, maybe a variable in .CI/config could store a timestamp that forces a cache clear if any files/folders are older.

Would be nice to have a cli utility to perform tasks independently of the git repo.

• test builds, with and without interfere
• verify signatures
• clear / modify cached sources
• other tasks that would be inconvenient to perform with git

From @dr460nf1r3:

how about implementing build tests via MR? Like:

• passing the builder another branch to source pkgbuilds from
• test building the package but don't actually deploy them
• maybe transfer the archive from the landing zone to the staging repo location which @stackofprimes mentioned
• make passing builds a requirement for merging MRs
  I imagine this decreases maintainers time spent with test building packages and also prevents bad PKGBUILDs ending up in main

This could also run a few other checks to ensure noticing potential issues.

Another benefit could be being the base for staging rebuilds, eg. we bump packages and move them to the prod repo once the MR has been merged?

Another implementation possibility is to have a command line utility that is run after logging on to the build server, similar to chaotic v3.