Showing content from https://github.com/jenkinsci/forensics-api-plugin below:
jenkinsci/forensics-api-plugin: Jenkins plug-in that defines an API to mine and analyze data from a source control repository
Jenkins Forensics API Plugin
This Forensics API Jenkins plug-in defines an API to mine and analyze data from a source control repository.
This API plugin provides the following services:
- Blames: Shows what revision and author last modified a specified set of lines of a file. This information can be used to track the original commit that introduced a piece of code.
- File statistics: Incrementally collects global commit statistics for all repository files in the style of Code as a Crime Scene [Adam Tornhill, November 2013]. This includes:
- commits count
- different authors count
- creation time
- last modification time
- lines of code (from the commit details)
- code churn (changed lines since created)
- Commit tracking: Tracks all new commits that are part of a build. Using this information plugins can search for builds that contain a specific commit.
- Commit statistics: Collects commit statistics for all new commits in a build or in a series of builds (e.g. for all commits of a pull request). This includes:
- commits count
- changed files count
- added and deleted lines
- Reference build: Several plugins that report build statistics (test results, code coverage, metrics, static analysis warnings) typically show their reports in two different ways: either as absolute report (e.g., total number of tests or warnings, overall code coverage) or as relative delta report (e.g., additional tests, increased or decreased coverage, new or fixed warnings). In order to compute a relative delta report a plugin needs to carefully select the other build to compare the current results to (a so called reference build). For simple Jenkins jobs that build the main branch of an SCM the reference build will be selected from one of the previous builds of the same job. For more complex branch source projects (i.e., projects that build several branches and pull requests in a connected job hierarchy) it makes more sense to select a reference build from a job that builds the actual target branch (i.e., the branch the current changes will be merged into). Here one typically is interested what changed in a branch or pull request with respect to the main branch (or any other target branch): e.g., how will the code coverage change if the team merges the changes. Selecting the correct reference build is not that easy, since the main branch of a project will evolve more frequently than a specific feature or bugfix branch.
- Repository Browser: Provides a RepositoryBrowser for commits. Since the original Jenkins interface has no API to generate links to simple commits, this decorator adds such a functionality. Note that this API does not only obtain such links, it also renders these links as HTML
a tags.
Jenkins Git Forensics Plugin is a plugin that implements the corresponding extension points for Git. Other version control systems are not yet supported.
Currently this API is only implemented by the Jenkins Git Forensics Plugin so please refer to the documentation there on how to use the features.
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4