curl -kv -X PUT https://<servername>/publish/coverage -d '{"lines": <n>, "covered": <m>, "project": "<project-name>", "subproject": "<subproject-name>", "language": "<language>"}' -H "Content-Type: application/json" -H "auth-token: <publish-auth-token>"
Only the last PUT of the day is remembered by the statistic server.
curl -kv https://<servername>/statistics/coverage/latest/<project-name> -H "auth-token: <statistics-auth-token>"
Provides you with the most recent coverage data for project <project-name>. Goes back max. 30 days into the past (in order to search for coverage-data). Aggregates coverage data throughout subprojects and languages in <project-name>.
curl -kv https://<servername>/statistics/diff/coverage/<project-name> -H "auth-token: <statistics-auth-token>"
Returns a coverage diff in this JSON-format: {"diff-percentage": 0.1, "diff-lines": 42, "diff-covered": 300}
The diff is calculated between todays coverage data (as returned by .../coverage/latest) and the previous
workdays coverage data. Workday is used under the assumption that coverage data will not change on a weekend :)
Before project can push coverage data to the stastistic server they have to be registered. Project can managed via this API:
curl -kv -X PUT https://<servername>/meta/project -d '{"project": "<project-name>", "subproject": "<subproject-name>", "language": "<language>"}' -H "Content-Type: application/json" -H "auth-token: <meta-auth-token>"
Register (project, sub-project, language) with the statistic server. You may not publish data before registering.
curl -kv https://<servername>/meta/projects -H "Content-Type: application/json" -H "auth-token: <meta-auth-token>"
Return a list of all projects known by the statistic server in the format: {"projects": [{"project": "foo", "subprojects": [{"subproject": "bar", "languages": [{"language": "java"}, {"language": "clojure"}]}, {"subproject": "baz", "languages": ...}"
At the moment you still have to copy the UI: resources/public from https://github.com/freiheit-com/fdc-web-test-monitor.
Use ./build.sh to build the docker image. The image will be tagged with :latest and :$VERSION, with $VERSION being the same in build.sh and project.clj
Or to build the jar directly:
lein uberjar (needs https://github.com/weavejester/lein-ring)
How to locally test the docker image is described in LOCAL_TESTING
After building the project use ./push.sh to push the :latest tagged image to the docker registry and restart the service. The image will be tagged with :latest in the registry.
To talk to the kube cluster (for rescaling) you will have to enter username and password. These should be fetched for you from the cluster and printed to the command line at the beginning of ./push.sh