Git software configuration management for Jenkins
- see Jenkins wiki for detailed feature descriptions
- use JIRA to report issues / feature requests
The master branch is the primary development branch for the git plugin.
Plugin source code is hosted on GitHub. New feature proposals and bug fix proposals should be submitted as pull requests. Fork the repository, prepare your change on your forked copy, and submit a pull request. Your pull request will be evaluated by the Cloudbees Jenkins job.
Before submitting your pull request, please assure that you've added a test which verifies your change. There have been many developers involved in the git plugin and there are many, 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.
Before submitting your change, please review the findbugs output to assure that you haven't introduced new findbugs warnings.
$ java -version # Need Java 1.8, earlier versions are unsupported for build
$ mvn -version # Need a modern maven version; maven 3.2.5 and 3.5.0 are known to work
$ mvn clean install- Fix bugs
- Improve code coverage
- Improve javadoc