Agenda

1. A short history of pbulk
2. Modern requirements
3. Configuration template
4. Impact of configuration choices
5. Current work
6. Future work

A short history of pbulk

• Project from Google's Summer of Code 2007
• Goal: Provide binary packages and regression tests
• Requirements:
  • Parallel builds using sandboxes (chroot, jail, zone)
  • Distributed builds in a LAN
  • Reproducable builds
  • Customizable build
• Assumptions:
  • Ressource sharing via null mounts, NFS
  • Restartable builds
  • Start-and-forget use

Modern requirements

• Shared filesystems ↔ explicit file transfers
• Fast rescanning
• Master may run on different platform
• Semi-interactive use for developers
• Package signing
• Intelligent scheduling

Current work

• Move up-to-date check into the master
• Move data storage into SQLite database
• ...significantly reduces memory footprint
• ...checksum based up-to-date check
• Integrate idle process monitor
• ...hello GNU make 4.2.1
• Figure out how to best compute ressource consumption

Future work

• Moving to HTTP(S) based communication protocol
• ...with integrated package/log upload
• ...and a nice web GUI for progress reports
• New scheduler based on ressource consumption

Q&A