This table details all available data for project
Main data available for project includes:
13information [ Display | Download JSON ]
81metrics [ Display | Download JSON ]
8attributes [ Display | Download JSON ]
26recommendations [ Display | Download JSON ]
A lot of information is also directly available from the plugins:
|ITS issues changed lifetime||ITS_CHANGED||Number of updates on issues during the overall time range covered by the analysis.||83|
|ITS issues changers lifetime||ITS_CHANGERS||Number of distinct identities updating tickets during the overall time range covered by the analysis.||14|
|ITS issues closed lifetime||ITS_CLOSED||Number of issues closed during the overall time range covered by the analysis.||55|
|Number of issue closed during last month||ITS_CLOSED_30||Number of distinct identities opening tickets during the last month in the issue tracking system.||0||1|
|ITS issue closers lifetime||ITS_CLOSERS||Number of distinct identities closing tickets during during the overall time range covered by the analysis.||5|
|ITS closers||ITS_CLOSERS_30||Number of distinct identities closing tickets during the last month in the issue tracking system.||0||1|
|ITS issues opened lifetime||ITS_OPENED||Number of issues opened during the overall time range covered by the analysis.||52|
|ITS issue openers lifetime||ITS_OPENERS||Number of distinct identities opening tickets during the overall time range covered by the analysis.||14|
|ML authors||MLS_SENDERS_30||Number of distinct senders for messages dated during the last month, in developer mailing list archives.||0||1|
|ML posts||MLS_SENT_30||Number of messages dated during the last month, in developer mailing list archives.||0||1|
|ML sent responses||MLS_SENT_RESPONSE||Number of responses (i.e. replies in a thread) in developer mailing list archives.||9||3|
|ML threads||MLS_THREADS||Number of threads (i.e. an email and its replies) in developer mailing list archives.||36||4|
|ITS information||PMI_ITS_INFO||Is the bugzilla info correctly filled in the PMI records?||5||5|
|SCM information||PMI_SCM_INFO||Is the source_repo info correctly filled in the PMI records?||0||1|
|SCM committers||SCM_AUTHORS_30||Total number of identities found as authors of commits in source code management repositories dated during the last three months.||2||3|
|SCM Commits||SCM_COMMITS_30||Total number of commits in source code management repositories dated during the last three months.||2||2|
|SCM Files committed||SCM_FILES||Total number of files touched by commits in source code management repositories dated during the last three months.||440||4|
|Activity||QM_ACTIVITY||The activity of the project's ecosystem, as measured on the mailing lists and configuration management system.||2.3||3 / 3|
|Diversity||QM_DIVERSITY||The diversity of the project's ecosystem, as measured on the mailing lists and configuration management system.||2.0||2 / 2|
|Ecosystem||QM_ECOSYSTEM||The sustainability of the ecosystem evolving around the project.||2.6||7 / 7|
|Change Management||QM_ITS||Do the project applies best practices regarding change management?||2.3||3 / 3|
|Process||QM_PROCESS||The maturity of the process used to run the project.||2.1||6 / 6|
|Project Maturity||QM_QUALITY||The overall Maturity of the project.||2.4||13 / 13|
|Configuration Management||QM_SCM||The maturity of the project regarding access and usage of the configuration management system.||2.0||3 / 3|
|Support||QM_SUPPORT||The amount of knowledge provided when someone asks for support.||3.5||2 / 2|
|PMI_EMPTY_DOC||PMI_EMPTY_DOC||The documentation URL is empty in the PMI. It helps people use, and contribute to, the project and should be correctly filled.||Low (1)||1|
|PMI_EMPTY_DOWNLOAD||PMI_EMPTY_DOWNLOAD||The download URL is empty in the PMI. People need it to download, use, and contribute to the project and should be correctly filled.||High (3)||1|
|PMI_EMPTY_GETTING_STARTED||PMI_EMPTY_GETTING_STARTED||The getting started URL is empty in the PMI. It helps people use, and contribute to, the project and should be correctly filled.||Low (1)||1|
|PMI_EMPTY_PLAN||PMI_EMPTY_PLAN||The plan document URL is empty in the PMI. It helps people understand the roadmap of the project and should be filled.||Low (1)||1|
|PMI_EMPTY_TITLE||PMI_EMPTY_TITLE||The title entry is empty in the PMI.||Medium (2)||1|
|PMI_EMPTY_UPDATE||PMI_EMPTY_UPDATE||The update site URL is empty in the PMI. People need it if they want to use the product, and it should be filled.||High (3)||1|
|PMI_NOK_CI||PMI_NOK_CI||The Hudson CI engine URL [https://hudson.eclipse.org/gendoc/job/Gendoc/] in the PMI is not detected as the root of a Hudson instance.||High (3)||1|
|CI_FAILING_JOBS||CI_FAILING_JOBS||Job Gendoc-nightly has been failing for more than 1 week. You should either disable it if it's not relevant anymore, or fix it.||High (3)||1|
|PMD_FIX_FILE||PMD_FIX_FILE||The file . . ents/src/org/eclipse/gendoc/documents/XMLDocumentService.java has only 1 P1 violations and 7 P2 violations. It would be quite easy to fix these in one shot and seriously improve the file's quality.||Low (1)||10|
|PMD_FIX_RULE||PMD_FIX_RULE||PMD rule AvoidBranchingStatementAsLastInLoop has only a few violations (1) and a high priority (2). It would be easy to work on this rule and the associated good practice, both for the project and for the team experience, and fix all violations associated to this rule.||Low (1)||5|
The PMI file as returned by the Eclipse repository (JSON).
The list of PMI checks and their results (CSV).
The list of PMI checks and their results (JSON).
The PMD configuration file retrieved for the analysis (XML).
The PMD results file retrieved for the analysis (XML).
Files: for each non-conform file, its name, total number of non-conformities, number of non-conformities for each priority, number of broken and clean rules, and the rate of acquired practices (CSV).
Generic information about the project : PMD version, timestamp of analysis, number of non-conformities, number of rules checked, number of rules violated, number of clean rules, rate of acquired practices (CSV).
Rules: number of non-conformities for each category of rules and priority (CSV).
Rulesets detected in analysis output, with number of violations for each priority, in long format (CSV).
Rulesets detected in analysis output, with number of violations for each priority, in wide format (CSV).
Violations: foreach violated rule, its priority, the ruleset it belongs to, and the volume of violations (CSV).
Violations: foreach violated rule, its priority, the ruleset it belongs to, and the volume of violations (JSON).
|Hudson||History of Hudson builds (HTML)||/projects/modeling.gendoc/Hudson/hudson_hist.html|
|Hudson||Pie of jobs statuses (HTML)||/projects/modeling.gendoc/Hudson/hudson_pie.html|
|PmdAnalysis||Non-conforimities by file (SVG)||/projects/modeling.gendoc/PmdAnalysis/pmd_analysis_files_ncc1.svg|
|PmdAnalysis||Pie of PMD analysis results (HTML)||/projects/modeling.gendoc/PmdAnalysis/pmd_analysis_pie.html|
|PmdAnalysis||Top 5 rules with most non-conformities (SVG)||/projects/modeling.gendoc/PmdAnalysis/pmd_analysis_top_5_rules.svg|
|PmdAnalysis||Repartition of non-conformities across rulesets (SVG)||/projects/modeling.gendoc/PmdAnalysis/pmd_configuration_rulesets_repartition.svg|
|PmdAnalysis||Pie of PMD configuration results (HTML)||/projects/modeling.gendoc/PmdAnalysis/pmd_configuration_summary_pie.html|
|PmdAnalysis||Non-conformities by rule (SVG)||/projects/modeling.gendoc/PmdAnalysis/pmd_configuration_violations_rules.svg|
Page generated by Alambic 3.3.2 on Tue Sep 19 14:56:35 2017.