Dan Cryer

Hi @dmtr81 - The build table's project_id column is already set as a foreign key to the project table, which is set to CASCADE both updates and deletes.

I tend to squash the history into one commit if I'm not interested in testing all of the distinct commits... Generally though we push individual commits to branches on an...

The best solution here is to use the daemon mode, by running `daemonise phpci:daemonise` instead of running `console phpci:run-builds` on a cron job. The daemon mode will only run one...

There isn't presently, no. I'm open to adding this kind of logic, but it isn't there now.

On the hosted service, we have multiple copies of the daemon running, so you get parallel builds, but each builder only runs one build at a time. That could work...

This was something I've wanted to do from the beginning (it's even in the README) - but as @meadsteve says, it's a big piece of work, so we really need...

P.s. I don't mind adding dependencies like this as long as they are optional. Not everyone needs to do multi-version testing, so PHPCI should continue to function as it does...

The dependencies thing has come up before, and I agree, PHPCI is already a different project to what it was when I started it a few months ago. At the...

The actual implementation will let you use whatever method you so choose. We'll simply provide the ability to create multiple builds for different platforms, it's up to you how you...

I'm not quite sure what you mean here. Please could you add a little more detail?