Table of Contents
Never report security issues on GitHub, public Jira issues or other public channels (Gitter/Twitter/etc.), follow the instruction from Jenkins Security to report it on Jenkins Jira. For issues related to Jenkins infrastructure services, please report them on Jenkins Infrastructure Help Desk.
In the Jenkins project we appreciate any kind of contributions: code, documentation, design, etc. Any contribution counts, and the size does not matter! Check out the contributing page for more information and links!
Many plugins and components also define their own contributing guidelines and communication channels. There is also a big number of chat channels and threads on the community forums.
| NOTE: This is a default CONTRIBUTING page for all repositories in Jenkins. Every plugin/component is its own sub-project which may deviate in its rules. Guidelines and channel links in repository CONTRIBUTING/README pages, if any, take precedence over this page. |
|---|
If you are a newcomer contributor and have any questions, please do not hesitate to ask in the Newcomers Gitter channel.
- For larger contributions create an issue for any required discussion
- Implement solution on a branch in your fork
- Make sure to include issue ID (if created) in commit message, and make the message speak for itself
- Once you're done create a pull request and ask at least one of the maintainers for review
- Remember to title your pull request properly as it is used for release notes
The prerequisites for Java and Maven are documented on the preparation page on jenkins.io.
See IDE configuration.
- Use the below commands.
$ mvn hpi:run ...
INFO: Jenkins is fully up and running
- Open http://localhost:8080/jenkins/ to test the plugin locally.
Some plugins use multi module maven builds and you may need to change your hpi:run command to be run from the child directory, and build the other modules first.
$ mvn install -P quick-build
$ mvn -f plugin hpi:run