Goal: Make Continuum "workflow oriented"
(from Trygve)
Steps:
o Turn the gut DefaultContinuum into a set of actions
o DefaultContinuum should just call workflows that's whose name is the same as the method in Continuum
o Make sure that the actions are (very) generic. The actions will become the building blocks for people that's extending Continuum. Changing the workflows should be the primary way/first place you start to customize Continuum.
Result:
- Continuum becomes a simpler system with some core functionality:
- Cron/Scheduler facility. This will trigger named workflows
- User authentication and autorization
- Notification
- Synchronous SCM functionality
- Synch because there should be actions around this functionality to give the async part around the SCM calls.
- It will become much easier to reuse and customize Continuum. It will also prepare Continuum for the future, and will make it much easier making different variants of Continuum
- Think variants like:
- Continuum: This is what we have today. The "easy to use, all in one" thing.
- Continuum Web Frontend: A simple web app that's just the users graphical interface to Continuum. This variant will just query the builder but remain responsive during builds.
- Continuum Core Server: A server with the database, the scheduler and the misc other core functionality
- Continuum Build Controller: Nodes where the checkouts are, which performs the builds
- Think variants like:
Labels