Dog-Fooding: Build BuildStream with BuildStream

Background

Also posted to the mailing list about this, and then followed up on in another thread.

I think there are some clear benefits to dog-fooding:

• Demonstrate confidence in BuildStream.
• Increase the amount of real world use cases, thus identifying more bugs.
• Mitigating against the risk of developers working 'in a vacuum', by ensuring developers are also users of the tool.

There is a risk that this will prove more difficult than anticipated, and potentially serve as a distraction that does not bring as much benefit as desired, but I think this risk is quite low, overall.

Having spoken to people informally about this, there seems to be a general consensus that this is clearly a good idea, but BuildStream is probably not yet ready for it at the moment.

If there is something you know of which blocks dog-fooding, I ask for your contributions here to help me identify that. Please could I request that you link from this issue to any already open issue which is blocking dog-fooding from happening, or open up a new issue if something is not already captured.

Task description

• Build BuildStream using BuildStream.

I plan to expand this once the specifics of the task become clearer...

Acceptance Criteria

• Link to a subgroup in gitlab for the example project
• Successful demo of buildstream being built using buildstream

I plan to expand this once the specifics of the task become clearer...