3r1co / fabric8-forge

Supports JBoss Forge plugins for the Fabric8 iPaaS along with using Forge as a REST service inside Fabric8 DevOps

Fabric8 Forge

This project contains the Fabric8 extensions for JBoss Forge. It includes:

• addons are various Forge addons for working with Apache Camel and Fabric8 DevOps
• rest provides a REST service for working with JBoss Forge with Fabric8 DevOps inside the Fabric8 Console

Documentation

For more details see the Fabric8 Forge Documentation

Building the addons

To try out addons:

cd addons
mvn install

Then you can install the addons into forge via the forge addon-install command using the current snapshot build version

Trying the addons locally

If you startup forge you can then install the local builds of the addons via:

addon-install --coordinate io.fabric8.forge:camel,2.2.113-SNAPSHOT
addon-install --coordinate io.fabric8.forge:camel-commands,2.2.113-SNAPSHOT
addon-install --coordinate io.fabric8.forge:devops,2.2.113-SNAPSHOT

To remove any of them type:

addon-remove --addons io.fabric8.forge:camel,2.2.113-SNAPSHOT
addon-remove --addons io.fabric8.forge:camel-commands,2.2.113-SNAPSHOT
addon-remove --addons io.fabric8.forge:devops,2.2.113-SNAPSHOT

Building and testing REST service

To build everything and run it in your local OpenShift installation on your laptop try:

mvn -Pf8-local-deploy

To push the docker image first then provision it onto a remote OpenShift cluster try:

mvn -Pf8-deploy

If you just want to build the docker image and kubernetes resources but not deploy them use:

mvn -Pf8-build

The test case in the fabric8-forge module takes a while to build as it pre-populates the local maven repository with all the required jars for the Forge tooling.

So you might want to only include tests in the fabric8-forge module the first build of the day, then disable tests after that?