Bump version

BUILD_SERVERS.md

@@ -2,17 +2,17 @@
 
 Prerequisite is a download of build-facts:
 
-    $ curl -LO https://github.com/cburgmer/build-facts/releases/download/0.2.0/build-facts-0.2.0-standalone.jar
+    $ curl -LO https://github.com/cburgmer/build-facts/releases/download/0.3.0/build-facts-0.3.0-standalone.jar
 
 ## Concourse
 
 Authentication with Concourse relies on Concourse's `fly` CLI. You can download
 it from your Concourse instance's main page. To get started run
 
     $ fly login --target build-facts -c http://localhost:8080          # replace with your Concourse URL
-    $ java -jar build-facts-0.2.0-standalone.jar concourse build-facts
+    $ java -jar build-facts-0.3.0-standalone.jar concourse build-facts
 
-See `java -jar build-facts-0.2.0-standalone.jar concourse --help` for more
+See `java -jar build-facts-0.3.0-standalone.jar concourse --help` for more
 options.
 
 
@@ -26,9 +26,9 @@ Test results will be picked up automatically if
 [published as a JUnit XML report file](https://www.go.cd/documentation/user/current/configuration/dev_upload_test_report.html).
 
     $ GOCD_USER="..." GOCD_PASSWORD="..." \
-          java -jar build-facts-0.2.0-standalone.jar gocd http://localhost:8153/go    # replace with your GoCD URL
+          java -jar build-facts-0.3.0-standalone.jar gocd http://localhost:8153/go    # replace with your GoCD URL
 
-See `java -jar build-facts-0.2.0-standalone.jar gocd --help` for more options.
+See `java -jar build-facts-0.3.0-standalone.jar gocd --help` for more options.
 
 
 ## Jenkins
@@ -39,9 +39,9 @@ parameters as offered by the
 [Parameterized Trigger Plugin](https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin).
 
     $ JENKINS_USER="..." JENKINS_PASSWORD="..." \
-          java -jar build-facts-0.2.0-standalone.jar jenkins http://localhost:8080    # replace with your Jenkins URL
+          java -jar build-facts-0.3.0-standalone.jar jenkins http://localhost:8080    # replace with your Jenkins URL
 
-See `java -jar build-facts-0.2.0-standalone.jar jenkins --help` for more
+See `java -jar build-facts-0.3.0-standalone.jar jenkins --help` for more
 options.
 
 
@@ -54,11 +54,11 @@ reporter" option selected), or via "Build Features" with "XML report processing"
 configured to pick up `*.xml` test artifacts generated by the test run.
 
     $ TEAMCITY_USER="..." TEAMCITY_PASSWORD="..." \
-          java -jar build-facts-0.2.0-standalone.jar teamcity http://localhost:8111 -p PROJECT_NAME    # replace with your TeamCity URL and project name
+          java -jar build-facts-0.3.0-standalone.jar teamcity http://localhost:8111 -p PROJECT_NAME    # replace with your TeamCity URL and project name
 
 Due to https://youtrack.jetbrains.com/issue/TW-45063 the option via Rake & RSpec
 will not provide a great level of detail for test results, so going the extra
 mile and using the workaround provided in the issue linked will help here.
 
-See `java -jar build-facts-0.2.0-standalone.jar teamcity --help` for more
+See `java -jar build-facts-0.3.0-standalone.jar teamcity --help` for more
 options.

README.md

@@ -3,8 +3,8 @@
 Download build facts from different CI/CD servers in a standard JSON schema.
 You then take it from there with your own analytics.
 
-    $ curl -LO https://github.com/cburgmer/build-facts/releases/download/0.2.0/build-facts-0.2.0-standalone.jar
-    $ java -jar build-facts-0.2.0-standalone.jar jenkins http://localhost:8080
+    $ curl -LO https://github.com/cburgmer/build-facts/releases/download/0.3.0/build-facts-0.3.0-standalone.jar
+    $ java -jar build-facts-0.3.0-standalone.jar jenkins http://localhost:8080
     Finding all builds for syncing from http://localhost:8080 (starting from 2021-01-06T23:00:00.000Z)...
     {"jobName":"Test","buildId":"1","start":1615151319678,"end":1615151342243,"outcome":"pass","inputs":[{"revision":"9bb731de4f4372a8c3b4e53e7d70cd729b32419c","sourceId":"https://github.com/cburgmer/buildviz.git"}]}
     {"jobName":"Test","buildId":"2","start":1615151342348,"end":1615151344854,"outcome":"pass","inputs":[{"revision":"9bb731de4f4372a8c3b4e53e7d70cd729b32419c","sourceId":"https://github.com/cburgmer/buildviz.git"}]}

examples/README.md

@@ -21,8 +21,8 @@ Bring up a server (adapt with the desired build server)
 
 Sync data
 
-    $ curl -LO https://github.com/cburgmer/build-facts/releases/download/0.2.0/build-facts-0.2.0-standalone.jar
-    $ java -jar build-facts-0.2.0-standalone.jar jenkins http://localhost:8080
+    $ curl -LO https://github.com/cburgmer/build-facts/releases/download/0.3.0/build-facts-0.3.0-standalone.jar
+    $ java -jar build-facts-0.3.0-standalone.jar jenkins http://localhost:8080
 
 Stop a server
 
@@ -47,6 +47,6 @@ Sync data from the build server into Splunk
 
     while read event; do
       curl -d "$event" -k -H "Authorization: Splunk 1234567890qwertyuiop" 'https://localhost:8088/services/collector'
-    done <<< "$(java -jar build-facts-0.2.0-standalone.jar jenkins http://localhost:8080 --splunk)"
+    done <<< "$(java -jar build-facts-0.3.0-standalone.jar jenkins http://localhost:8080 --splunk)"
 
 An example [dashboard exists](./splunk/dashboard.xml) and can be copied in via the "Source" edit mode.

project.clj

@@ -1,4 +1,4 @@
-(defproject build-facts "0.2.0"
+(defproject build-facts "0.3.0"
   :description "Dump your build pipeline's data for inspection"
   :url "https://github.com/cburgmer/build-facts"
   :license {:name "BSD 2-Clause"