Git software configuration management for Jenkins.
- see Jenkins Wiki for feature descriptions
- use Jenkins JIRA to report issues or request features
- Jenkins
2.138.4
or newer
The master
branch is the primary development branch.
Branches using name pattern stable-{VERSION}
are development branches
for changes from a base release VERSION
. For example stable-3.x
is the
branch used to release fixes for plugin version 3.x
.
To build the plugin you will need
- Maven version
3.5.4
or newer - Java Development Kit (JDK) version
8
or version11
Run the following command to build the plugin (Java 8)
mvn package
Run the following command to build the plugin (Java 11)
mvn -Djenkins.version=2.164.1 package
Plugin source code is hosted on GitHub.
New feature proposals and bug fix proposals should be submitted as
pull requests.
Fork the repository. Make the desired changes in your forked copy. Submit
a pull request to the master
branch. Your pull request will be evaluated
by the Jenkins job.
Before submitting your pull request, please add tests which verify your change. There have been many developers involved in the git plugin and there are many users who depend on the git plugin. Tests help us assure that we're delivering a reliable plugin and that we've communicated our intent to other developers in a way that they can detect when they run tests.
Code coverage reporting is available as a maven target and is actively
monitored. Please improve code coverage with the tests you submit.
Code coverage reporting is written to target/site/jacoco/
by the maven command
mvn -P enable-jacoco clean install jacoco:report
Before submitting your change, review the SpotBugs output to assure that you haven't introduced new warnings.
mvn spotbugs:check
- Fix bugs
- Improve code coverage
- Improve javadoc