Hi Butch

Individual consolidations that form OpenIndiana distribution are using different build systems. Some consolidations are available in binary form only.

I propose creating a unified infrastructure on top of all build systems so that full or incremental builds of the whole OS could be done with a single command.

I don't have much experience with continuous build systems but I suspect such infrastructure could be used with something like Hudson/Jenkins. I am sure Jenkins can start make command after noticing a change in the version control system.

Andrzej

On 03/16/11 15:34, Butch Whitby wrote:
I've been following the list for a while now, and have kept quiet
partially due to time constraints, but mostly because I think I'm
going to be most helpful in the documentation arena but I have a
couple of questions about this.

Please overlook my ignorance on this topic I'm an admin not a
programmer and have zero experience with continuous build systems.   I
have limited understanding of how they actually work,  and haven't had
the time to really dig into the topic.  It seems there are a lot of
"auto builders" available already.  At a cursory glance I can see it's
a far cry from a simple setup but would definitely be worth doing
right.  Am I misunderstanding or are you proposing to use a continuous
integration system for this? Would something like Hudson be viable?

Or are you talking about developing a framework that could be provided
in a packaged form for download to a developers system?  Or even a
combination of both?

I'll help in any way I can.

_______________________________________________
oi-dev mailing list
[email protected]
http://openindiana.org/mailman/listinfo/oi-dev

Reply via email to