CONTRIBUTING 1.4 KB
Newer Older
1
=== Contributing code to this project
2 3

It's helpful to track fixes or new features via wishlist bugs against the
4
'jenkins.debian.org' package, eg with the 'reportbug' tool ('devscripts' package).
5
The BTS will ensure the developers' mailing list
6
   qa-jenkins-dev@lists.debian.org
7 8
is notified.

9
The code is available in the link:https://anonscm.debian.org/git/qa/jenkins.debian.net.git/tree/[jenkins.debian.net.git repository].
10

11 12 13 14
Patches can be submitted as requests to pull from a publicly-visible 
git repository (this is the prefered way) communicated via IRC or mail,
or completly via mail (using git format-patch, see below).
If appropriate, please make a topic branch based on the 'master' branch.
15

Mattia Rizzolo's avatar
Mattia Rizzolo committed
16
You can send patches or requests to the link:mailto:qa-jenkins-dev@lists.alioth.debian.org[development list],
17 18 19
or to the tracking bug: <bugnumber>@bugs.debian.org.

One possible workflow:
Holger Levsen's avatar
Holger Levsen committed
20
----
Mattia Rizzolo's avatar
Mattia Rizzolo committed
21
  git clone git://anonscm.debian.org/qa/jenkins.debian.net.git
22
  git checkout origin/master -b <topicname>
Holger Levsen's avatar
Holger Levsen committed
23
  # <edits>
24 25 26
  git commit -a
  git format-patch -M origin/master

27
  reportbug jenkins.debian.org
Holger Levsen's avatar
Holger Levsen committed
28 29
  # <describe the issue, attach the patch>
----
30

31 32
=== Contributing bugs to other projects

33 34
Another very useful type of contributions are filing bug reports based
on jenkins job runs. Another useful kind of contribution would be to
35
improve the documentation, eg to better describe how to debug stuff.
36 37

// vim: set filetype=asciidoc: