firehose connects to (micro) services (Thin WARs), gathers monitoring data and provides it in prometheus-compliant format. Lacking metadata
can be provided via environment variables at docker start or via HTTP / JSON at runtime. New endpoints can be re-configured on-the-fly.
One firehose instance can handle multiple endpoints. Firehose is a 16 kB Java EE 7, zero dependency, Thin WAR.
Browsersync will open chrome, serve static files (polymer libs) from bower_components folder and
watch src folder. Any changes are going to be automatically pushed to the browser without reloading.
Skip the bower_components folder in all imports:
The method input within the Jenkinsfile suspends the build and waits infinitely for the user
input with configurable options.
A Yes / No dialog waits for user input and returns true / false with the following code snippet:
def doesJavaRock = input(message: 'Do you like Java?', ok: 'Yes',
parameters: [booleanParam(defaultValue: true,
description: 'If you like Java, just push the button',name: 'Yes?')])
echo "Java rocks?:" + doesJavaRock
In this screencast I created from scratch with Maven, built (CentOS, JDK, Payara, Thin WAR, taken from docklands) and pushed a Full Profile Java EE 7 (Payara Full) application to Amazon EC2 Container Service cluster.
The ECS cluster is running on the smallest "free tier" available Amazon EC2 machine t2.micro (1 CPU and 1 GB RAM). t2.nano (512 MB max) would also work -- but is not eligible for free tier.