Version 0.1.4

Summary

This release integrates the CI/CD pipeline with Probe Dock. Test results are published on a shared project, available at https://trial.probedock.io/avaliasystems/openaffectserver. When other people contribute to the project, it will be necessary to work with additional API keys or even additional Probe Dock projects.

Functionality

No change.

Build process

• Jenkinsfile has been updated to display link to Probe Dock results
• BDD docker image has been update to publish XUnit test results to Probe Dock

Version 0.1.3

Summary

This release does not introduce any functional change. It introduces a CI/CD build pipeline implemented on top of Jenkins and Docker. The Jenkins server runs in a Docker container and, during the build process, starts a Docker topology with the new version of the server. It also starts a short-lived container that runs the API tests.

Functionality

No change.

Build process

• As indicated in the README.md file, it is possible to start the Jenkins server with docker-compose
• Once Jenkins is running, it is possible to launch a job that builds, runs and tests the server
• The setup uses the new declarative pipeline DSL from Jenkins

Version 0.1.2

Summary

Minor bug fixes.

Version 0.1.1

Summary

This release does not introduce any functional change. It introduces BDD-style tests for the REST API implementation. Cucumber-JVM has been used in a separate Java project (also built with maven). This project uses the swagger .yaml specification to generate client stubs at every build.

Functionality

No change.

Build process

• There is now a new Docker image that packages the executable specification
• After starting the topology (as in the previous release), it is possible to run a container based on this image to execute the API tests
• The test results are displayed on the console

Version 0.1.0

Summary

The first version of the server is very basic, both in terms of functionality and build process. However, it already supports the end-to-end process of submitting measures to the server, persisting them and later retrieving them.

Functionality

• The server exposes a /measures endpoint, which can be used to POST and GET measures.
• The endpoint does not handle pagination.
• The payloads are not validated.
• The payloads are stored in a MongoDB database

Build process

• There is no end-to-end CI pipeline yet (no jenkins)
• apache maven is used to build the Spring Boot application
• Swagger has been used to specify the REST API and the spec is used to regenerate stubs at every build
• There is no test, but a PostMan collection is provided for manual testing
• Docker is already in place