Skip to main content

Red Hat JBoss Fuse - Automate integration CI/CD processes

Long time no see :) , for many of you who knows me, I've been through a major change in life, moving to another country for couple of years, that is why there are less updates in my blog. But, I am back! Getting back to business. Fuse Integration Service 2.0 Tech preview was out two weeks ago, since this version is base on OpenShift 3.3, which has pipeline capability prebuilt on top of it (Tech preview on OpenShift as well). This get it one step closer to a more automated and agile continuous integration, and deployment one-stop platform for us, the integration developer.

For the pipeline to work on OpenShift, you will need Jenkins installed and running. OpenShift uses it to build, process and handle all the workflows. If you are familiar with developing in openshift, to build the pipeline is pretty simple and straight-forward. The pipeline is defined as a build configuration in OpenShift, just create a build config then import it to the namespace you want it to be in. And that is it.

This is what the build config looks like, note the strategy type is called JenkinsPipeline, this will trigger the interaction with Jenkins, and pushes the defined Jenkinsfile onto the server itself. The Jenkins Server will then interact with openshift and start the automated CI/CD process.

kind: BuildConfig
apiVersion: v1
  name: pipelinename
    name: pipelinename  
  - type: GitHub
      secret: secret101
  - type: Generic
      secret: secret101
    type: JenkinsPipeline
      jenkinsfile: "
        node('maven') { 
          stage('build') { 
            print 'build'
            openshiftBuild(buildConfig: 'buildconfigname', showBuildLogs: 'true')
          stage('staging') {
            print 'stage'
            openshiftDeploy(deploymentConfig: 'deploymentconfigame')     

As you can see on the above Jenkinsfile in the build configuration, it's interacting with the openshift itself through the OpenShift and Jenkins plugin. For instance, you could trigger to build an image, deploy the application through calling the deployment config, tag an image or even scale up and down the number of containers.

This upper part of the blog is pretty generic to most of the application running on OpenShift, but, HEY, Fuse Integration Service is just another application running on top of it. But this application just simply contains PATTERN BASE integration technology that has 160+ built-in components in it, so we smart developer don't have to waste time and energy on repetitive stuff, no big deal. :)
No matter what version you are using, this pipeline capability can help you automate your integration microservice.

Here is a small demo video that takes you through the entire process.


Popular posts from this blog

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.

2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.

So, now we know …

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.

And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.

And select JBoss Fuse Development for the plugin,

Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …