Description
Java code commit impact analysis, is a pure python library that analyzes the impact of two git submissions of Java projects on the project and generates tree chart data.
Github: jcci
Achieve Effect
Instructions
Start a new python project, add a new python file, code example:
from jcci.analyze import JCCI
# Compare different commits on the same branch
commit_analyze = JCCI('git@xxxx.git', 'username1')
commit_analyze.analyze_two_commit('master','commit_id1','commit_id2')
# To analyze the impact of methods in a class, use the analyze_class_method method. The last parameter is the line number(s) of the method(s) you want to analyze. If multiple methods are specified, separate their line numbers with commas. If left blank, it will analyze the impact of the entire class.
class_analyze = JCCI('git@xxxx.git', 'username1')
class_analyze.analyze_class_method('master','commit_id1', 'package\src\main\java\ClassA.java', '20,81')
# Compare different branches
branch_analyze = JCCI('git@xxxx.git', 'username1')
branch_analyze.analyze_two_branch('branch_new','branch_old')
At the same time, the project will be cloned in the directory and then analyzed to generate a file with the suffix format xxxx.cci, which contains the tree diagram data generated by the analysis results, download jcci-result.html , upload analyze result file end with .cci, then can be displayed through the view.
1 maintainer
Metadata
1 maintainer
Release files for jcci 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| jcci-0.2.1.tar.gz | 39.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jcci-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 76.7 kB
Release files / jcci-0.2.1.tar.gz
| Download URL | jcci-0.2.1.tar.gz |
|---|---|
| Size | 39.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a05612a4497fa6e63434ca157d4c87b9f724c2d781b3bc8734b6cb52b78796d9
|
|
BLAKE2b-256 checksum How to use checksums |
9669e7edd25ec9ad14de9caf2a7459b5976548047b5c91ca3baf2a6bea15afec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.2
|
Release files / jcci-0.2.1-py3-none-any.whl
| Download URL | jcci-0.2.1-py3-none-any.whl |
|---|---|
| Size | 37.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed648c4a354f9d18cad393b9d994d7b687fffcfaeee93c1947d5dd9b456a2df2
|
|
BLAKE2b-256 checksum How to use checksums |
72c8a1363042a79a3012b578f8ff54610b2f9ac7402dd8e50b3d8e9567d527ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.2
|
Security for jcci 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
