This repository has been archived by the owner on Feb 22, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
Home
Jan-Willem Gmelig Meyling edited this page Feb 23, 2016
·
13 revisions
This page describes some of the issues we want to tackle in the near future.
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.
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
commitsand pushes. - Allow assistants to merge / split groups, and move students between groups.
Write admin/deployment manual.Allow admin to kill stuck builds.Notify admins when build queues get stuck.Maven repository
- Provide overview of KPIs such as number of commits, coverage, number of test cases, percentage of passing builds, etc.
- 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.
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.