forked from plone/buildout.jenkins
/
README.txt
56 lines (36 loc) · 1.7 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
===============================================================================
JENKINS BUILDOUT FOR PLONE PROJECTS
===============================================================================
buildout.jenkins allows you to easiely set up a buildout that the Jenkins
CI-Server can use to generate reports for tests, test-coverage and
code-analysis.
Buildout
========
Create a jenkins.cfg that extends your existing buildout.cfg and set the
package-name parameter for the package that you want to be tested.
[buildout]
extends =
buildout.cfg
https://github.com/plone/buildout.jenkins/blob/master/jenkins.cfg
package-name = plone.app.discussion
package-directory = plone/app/discussion
Jenkins Job Shell Build Script
==============================
Configure a free-style Jenkins project and add a shell build script with the
following lines:
python2.6 bootstrap.py
bin/buildout -c jenkins.cfg
If you want Jenkins to run the test only, append the following line:
bin/jenkins-test
If you want Jenkins to run the test together with a test-coverage analysis,
append:
bin/jenkins-test-coverage
If you want Jenkins to run a code analysis, append:
bin/jenkins-code-analysis
PLUGINS
=======
- Clonedigger:
Setup of violations plugin
The final step, should be to bind the clonedigger's output with the Hudson. So, using the violations plugin, put the '**/clonedigger.xml' string to the CPD field in the violations plugin setup. The clonedigger with --cpd-output will generate PMD's cpd similar output. (I hope there is no problem their XML schema in clonedigger).
That should be all. Now run the build and watch for yourself! Enjoy.
http://clonedigger.sourceforge.net/hudson_integration.html