We are happy to take untested patches. Patches are reviewed before merging but no one has a complete test environment for all jobs, so please publish your well meant and untested patches as soon as they are ready!
1.1. Contributing code to this project
It’s helpful to track fixes or new features via wishlist bugs against the jenkins.debian.org package, e.g. with the reportbug tool (devscripts package). The BTS will ensure the developers' mailing list firstname.lastname@example.org is notified.
The code is available in the jenkins.debian.net GIT repository.
Patches can be submitted as requests to pull from a publicly-visible git repository (this is the preferred way) communicated via IRC or mail, or completely via mail (using git format-patch, see below). If appropriate, please make a topic branch based on the master branch.
You can send patches or requests to the development list, or to the tracking bug: <bugnumber>@bugs.debian.org.
One possible workflow:
git clone https://salsa.debian.org/qa/jenkins.debian.net git checkout origin/master -b <topicname> # <edits> git commit -a git format-patch -M origin/master reportbug jenkins.debian.org # <describe the issue, attach the patch>
1.2. Contributing bugs to other projects
Another very useful type of contributions is filing bug reports based on jenkins job runs. Another useful kind of contribution would be to improve the documentation, e.g. to better describe how to debug stuff.