|
|
|
|
|
As of today there are 1556 repositories at Eclipse. We need to define a good strategy to fetch them regularly, catch new repositories when they are created, and generally monitor their analysis.
|
|
|
|
|
|
## Requirements
|
|
|
|
|
|
* Continuously fetch, analyse and publish results for projects.
|
|
|
* Monitor execution, as it sometimes stales (e.g. when encountering a repo that requires credentials, or for whatever reason or bug).
|
|
|
|
|
|
## Options
|
|
|
|
|
|
* Setup a local Jenkins instance to execute runs, and our static website for results. \
|
|
|
Starting a run would be easy thanks to the jenkins UI, with tracking and monitoring of past runs, ability to automatically start jobs, etc.
|
|
|
* Write a dynamic (i.e. with active endpoints e.g. to start runs) frontend, which could be used both for control and reporting. \
|
|
|
Implies some heavy dev.
|
|
|
* Simply rely on crontabs for the update/execution of projects, and use our static website for results. \
|
|
|
Less visible, no easy way to start a run remotely or track job execution..
|
|
|
|
|
|
## Implementation
|
|
|
|