| XCTORY-1 |
|
|
Add unit tests to improve coverage | ||||||||||
| XCTORY-2 |
|
|
Add project creation and edition to the web UI | ||||||||||
| XCTORY-3 |
|
|
Add SCM integration | ||||||||||
| XCTORY-4 |
|
|
Improve Web UI | ||||||||||
| XCTORY-5 |
|
|
Authentication and Authorization | ||||||||||
| XCTORY-6 |
|
|
Add unit test to the web UI | ||||||||||
| XCTORY-7 |
|
|
Add form validation (client-side and server-side) | ||||||||||
| XCTORY-8 |
|
|
Review and document concurency | ||||||||||
The first design of xooctory has been made with concurrency in mind, but after reading the excellent book from Brian Goetz Java concurrency in practice, it appears that:
Using annotations used throughout the JCIP book would improve the documentation, and could be used to review which classes have been reviewed according to concurrency good practices detailed in the book. |
|||||||||||||
| XCTORY-9 |
|
|
review agent and jobs model | ||||||||||
| XCTORY-10 |
|
|
SCM Polling | ||||||||||
| XCTORY-11 |
|
|
review publishing architecture | ||||||||||
| XCTORY-12 |
|
|
JUnit reports | ||||||||||
| XCTORY-13 |
|
|
push is not working properly | ||||||||||
| XCTORY-14 |
|
|
use cometd as push mechanism | ||||||||||
| XCTORY-15 |
|
|
log auto update fix and improvement | ||||||||||
| XCTORY-16 |
|
|
Easy SCM URL configuration | ||||||||||
| XCTORY-17 |
|
|
deal with SCM authentication without displaying password in the SCM URL | ||||||||||
| XCTORY-18 |
|
|
change logs | ||||||||||
| XCTORY-19 |
|
|
remote agents | ||||||||||
| XCTORY-20 |
|
|
failure recovery | ||||||||||
| XCTORY-21 |
|
|
improve job distribution strategy | ||||||||||
| XCTORY-22 |
|
|
advanced job result sharing | ||||||||||
| XCTORY-23 |
|
|
user management UI | ||||||||||
| XCTORY-24 |
|
|
fine grain authorization based adaptation of UI | ||||||||||
| XCTORY-25 |
|
|
improve notifications | ||||||||||
| XCTORY-26 |
|
|
review concept of project: introduce job plan | ||||||||||
| XCTORY-27 |
|
|
search job plans | ||||||||||
| XCTORY-28 |
|
|
differential reporting | ||||||||||
| XCTORY-29 |
|
|
compilation report | ||||||||||
| XCTORY-30 |
|
|
workspace report | ||||||||||
| XCTORY-31 |
|
|
artifacts report | ||||||||||
| XCTORY-32 |
|
|
emma report | ||||||||||
| XCTORY-33 |
|
|
checkstyle report | ||||||||||
| XCTORY-34 |
|
|
PMD report | ||||||||||
| XCTORY-35 |
|
|
Findbugs report | ||||||||||
| XCTORY-36 |
|
|
javadoc report | ||||||||||
| XCTORY-37 |
|
|
replay job | ||||||||||
| XCTORY-38 |
|
|
label job | ||||||||||
| XCTORY-39 |
|
|
improve job progress bar | ||||||||||
| XCTORY-40 |
|
|
handle job dependencies | ||||||||||
| XCTORY-41 |
|
|
improve annotation results UI | ||||||||||
| XCTORY-42 |
|
|
Use Ivy to detect job dependencies | ||||||||||
| XCTORY-43 |
|
|
Improve annotation differential reporting | ||||||||||
| XCTORY-44 |
|
|
Review job plan page | ||||||||||
| XCTORY-45 |
|
|
Add summary tab to job page | ||||||||||
| XCTORY-46 |
|
|
Use change logs to fill in why and who fields in jobs | ||||||||||
| XCTORY-47 |
|
|
Add SCM logs to job logs | ||||||||||
| XCTORY-48 |
|
|
job activity | ||||||||||
| XCTORY-49 |
|
|
Improve change log details | ||||||||||
| XCTORY-50 |
|
|
Add inline documentation | ||||||||||
| XCTORY-51 |
|
|
Add success and failing time | ||||||||||
| XCTORY-52 |
|
|
Modularize xooctory | ||||||||||
