What can be done?
I've been thinking that most people really don't need a full clobber build all the time. If there is a 2 line fix somewhere, just verifying that the code builds and the resulting binaries work is most important - and most encouraging for the casual bug fixer. If there's a big re-work of Makefiles or changes are made to the linking of a program a full build may be more important. A service that can do incremental builds would be a big help.
So here's (very roughly) how I envision it.
Each time a release is tagged by a participating consolidation...
- A job is kicked off to build it on each supported architecture.
- A zfs snapshot is created of the workspace with the completed build.
- The completed build is packaged into an IPS repository
- Populate a workspace with the original source code
- Create a webrev
- Submit the webrev to the build system, saying which consolidation and build to build against and which architectures to build for
- Schedules the job via Hudson or Grid Engine.
- The job starts by cloning the pre-built release of the consolidation. Quite likely, it also clones then boots the proper boot environment.
- The patch included in the webrev is applied to the source
- An incremental build is done
- The pre-built IPS repository is cloned to a per-developer repository
- Packages associated with the changed files are populated into the per-developer IPS repository. The changed packages associated with this build are added as dependencies to a special package (e.g. build-20080611.0)
- Results are sent to the developer.
beadm create testbe beadm mount testbe /testbe pkg -R /testbe set-authority -O http://pkg.opensolaris.org/mysername myusername.opensolaris.org pkg -R /testbe install build-20080611.0 beadm unmount testbe beadm activate testbe init 6There are certainly plenty of details to work out. This is meant to be the start of a discussion to determine wether it is something worth pursuing and if so what those missing details are.