You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jan-Willem Gmelig Meyling edited this page Feb 23, 2016
·
13 revisions
Backlog
This page describes some of the issues we want to tackle in the near future.
Small Issues
Display full commit description and title consistently in interface.
Add a breadcrumb trail to allow users to easily go back to the selected group page.
Certain tags can include changes in a commit, but do not trigger a build.
Students can request a certain commit to be built.
Features
Comments / discussion on a tag.
In-line comments in diffs / code.
Historic trends on number of checkstyle warnings, junit results, coverage results, pmd, etc.
mvn site on e.g., just the tags for grading purposes.
Add a tag using the web-interface, to help students who don't understand pushing.
Display a date for commits and pushes.
Allow assistants to merge / split groups, and move students between groups.
Admin panel
Write admin/deployment manual.
Allow admin to kill stuck builds.
Notify admins when build queues get stuck.
Maven repository
Key Performance Indicators
Provide overview of KPIs such as number of commits, coverage, number of test cases, percentage of passing builds, etc.
Usage beyond TU Delft
At this moment: Deployment via Vagrant relatively easy.
Authentication is presently based on university-specific LDAP server. This already is configurable, but there is no account management page / way to create a user. Another possibility is to setup a separate LDAP server.
Scaleability
What if we run this on a massive scale?
Presently deployed on two VMs: One with git/devhub/1-buildserver; Other with 3-buildservers.
Need to conduct measurements what happens under massive load / stress.