A tool to assess the effort spent to develop software project and its readiness.
- Commit count per developer per week
- Churn (lines changed) per developer per week
- Owned code per developer per week
- Rework code done by developers
Credentials: admin/admin
./gradlew clean syncNpm build
./gradlew clean syncNpm build -x test bootRun
./gradlew clean syncNpm -x test bootJar
./gradlew clean syncNpm syncJar buildImage
- Ensure you have Java 11 installed
- Start Neo4j database i.e. using docker (ready to use sample deployment is in docker-compose.yml)
- Do Build and run (without tests) to start application
- Open UI at http://localhost:8080
- Login with
admin/admin
credentials
- Click on
Add Project Button
(OpenProjects
page from menu if necessary)
- Fill in new project to analyze details, click
Add
button when done
- Start project analysis - click
Restart analysis button
- Wait for analysis to be finished
- Create new user from aliases - open
User mappings
- Create new user from aliases - Create new user
- Create new user from aliases - merge aliases to user
- See the reports
package com.project_control.rules
import com.valb3r.projectcontrol.domain.rules.RuleContext
dialect "mvel"
rule "Only .java files"
no-loop
when
$c: RuleContext(path matches '.+\\.java')
then
$c.include = true;
update($c)
end
package com.project_control.rules
import com.valb3r.projectcontrol.domain.rules.RuleContext
dialect "mvel"
rule "Not in resources files"
no-loop
when
$c: RuleContext(path matches '.+/resources/.+')
then
$c.exclude = true;
update($c)
end