To gain productivity and raise the level of robustness to your design, this is a way of making members of your design team to focus on tasks and letting a server secure the code.

Running

Each member of the design team shall work as usual towards a common database creating test cases and build variants.

The server will continously check the database for changes. When changes are present the server will check out files and run the scripts on HEAD. Revision range between BASE and HEAD will be stored.

When errors occures the server will re-run scripts reporting errors on  revision range until revision with failure has been recognized.

Designer responsible for the check-in caused the failure will be assigned with the task to solve the problem. The designer may be innocent but is most suited for the task.

Everyone will be able to follow the current status of the latest run.

Containing

The following are example of tasks to be included in the continous run script:

• Documentation (register map, doxygen)
• Regression simulations (block, top, post)
• Build (default, variants, blocks)
• Validation (test on hardware)
• Delivery (file copy, check-in)

Impact

There are a minimum of changes required to be able to implement the continous run method:

• Scripts
• Settings
• Errors and warnings

Should not be included in the design file structure

Controling the scripts, can be apart of the design

Errors and warnings must report to the scripts, some simple rules