I published v0.1.0 of the plugin yesterday.

Documentation is available at http://brooklyncentral.github.io/brooklyn-maven-plugin/index.html.


On 05/01/2015 11:05, Sam Corbett wrote:
Hi,

I've recently published a Maven plugin for Brooklyn to help test application components: https://github.com/brooklyncentral/brooklyn-maven-plugin

It has three goals: deploy, sensor and stop. The expected workflow is:
* deploy: Deploy a blueprint to the configured server.
* sensor: Query a running application for the value of a sensor on an entity whose type matches a configurable regular expression. * Do something (e.g. run some tests) with the result of the sensor goal injected.
* stop: Terminate the deployment and release resources.

By default deploy and sensor run in the pre-integration-test phase and stop runs in the post-integration-test phase; the plugin makes most sense when run in conjunction with maven-failsafe-plugin. It currently expects Brooklyn to be running.

The repository includes an example project that demonstrates each goal with the deployment of a simple application. You should be able to try it by cloning the project, building, starting Brooklyn, switching to src/test/projects/example-app and running `mvn clean verify`. At the end you should see output like:

[INFO] --- maven-antrun-plugin:1.3:run (default) @ test ---
[INFO] Executing tasks
     [echo] Maven plugin example results:
     [echo] Application: T0tERELL
     [echo] Sensor value: http://127.0.0.1:8080/

My next step is to make a real release of the plugin.

Any feedback would be great.

Thanks,

Sam


Reply via email to