Hi Georgiy,
I've added Martin (the potential mentor) to Cc. Yes, Quartus is in the scope of this project area.
My recommendation would be to start from automating the flow for one of your student projects using built-in Jenkins features. FYI there is a
solution page, which may give you links to the current Jenkins & FPGA automation approaches.
In the case of Jenkins, we would be interested to get some advanced reporting and visualization.
Build steps are covered by Quartus CLI tools well, so IMHO it has lower priority (but can be implemented as well).
Examples for reporting features (aggregated thoughts from Martin and me):
* Timing report summary per build (worst case slack, total negative slack, total unconstrained paths, ?)
* Resource utilization (PLLs, LUTs, IOs, mems, etc.)
* Better visualization of Quartus build logs in Jenkins (keywords: Build Failure Analyzer Plugin, Log Parser, Collapsing Console Sections)
* Maybe: publishing of simulation reports and coverages from integrated tools like ModelSim-Altera
There
could be tabular reports per build (per run), and a trend plots per
project. The plugin could have the option to fail the build if the
timing report fails to meet some user specified criteria (e.g. designer
wants no unconstrained paths, a limit on worst case slack, max total
negative slack, etc).
Best regards,
Oleg Nenashev
вторник, 15 марта 2016 г., 19:08:19 UTC+1 пользователь Georgiy Zhemelev написал: