-
Notifications
You must be signed in to change notification settings - Fork 4
/
readme
31 lines (18 loc) · 1.24 KB
/
readme
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
You need to have Maven installed to build the plugin (use brew install maven on OSX).
Once Maven is available, update your settings.xml according to https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial
Afterwards you can build the plugin using Maven:
mvn install
After the first run, use -o to speed up that process:
mvn -o install
That puts a .hpi file into the target folder. Upload that to a Jenkins instance, or copy it manually to the plugins folder.
Afterwards you should be able to add "TestSwarm integration" as a build step to any type of project.
Fill in the empty fields, and a at least one testsuite. Then start a build and check the console output for results.
Testsuite URLs can use build and enviroment variables. For example, this:
http://swarm.jquery.org/git/jquery-ui/${GIT_COMMIT}/tests/unit/autocomplete/autocomplete.html
gets resolved to this:
http://swarm.jquery.org/git/jquery-ui/c1cda180a93a6c0a63cf21a68dacb54233e03d03/tests/unit/autocomplete/autocomplete.html
Other environment variables are documented on the Jenkins wiki: https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-JenkinsSetEnvironmentVariables
Legalese
--------
Copyright 2011 appendTo
Licensed MIT / GPL