Syndesis CLI

Buildtool “syndesis”

Syndesis uses a single tool for controlling various aspects of the build and developer related tasks. This script can be found in $SYNDESIS_DIR/tools/bin and is called syndesis. It requires bash and can be used on any Unix or macOS.

To have this script handy all the time it is recommended to either put this bin/ directory into the path or add a symlink from syndesis into a directory which is already on your execution path.

# Navigate to syndesis project directory

# Set path to include Syndesis' tool directory
$ export PATH=${PATH}:$(pwd)/tools/bin

# Alternatively, set a symbolic link to "syndesis"
$ ln -s $(pwd)/tools/bin/syndesis /usr/local/bin

The script can be used for various tasks which are selected by a so-called command_ which is the first argument to the script.

Just type syndesis -h to get an overview of the commands available:

Usage Message

Usage: syndesis <command> [... options ...]

with the following commands

   build             Build Syndesis
   completion        Shell completion
   crc               Initialize and manage a developer environment using OCP4 CodeReady Containers
   dev               Syndesis developer tools
   install           Install Syndesis to a connected OpenShift cluster
   integration-test  Run integration tests
   kamel             Tools for developing integrations using Camel K
   minishift         Initialize and manage a Minishift developer environment
   release           Perform a release
   system-test       Run system tests
   ui                Syndesis UI tasks

"build" is the default command if no command is specified.

Every sub command also offers usage information accessible using syndesis subcommand --help.

There are a handful of global options which can be used:

--help-hPrint usage information. If a command is given print out commands specific options.
--rebase-rRebase your project directory before building to integrate upstream changes to your local repository. See below for details how this works.
--verbose Set verbose mode, which is useful mostly only for debugging the script itself.

Rebase to Upstream

To easily rebase on changes which have been merged upstream to master, you can use the option --rebase (short: -r).

This command assumes that you have forked the Syndesis GitHub repositories and you have “origin” and “upstream” remotes like

$ git remote -v
origin    [email protected]:rhuss/syndesis.git (fetch)
origin    [email protected]:rhuss/syndesis.git (push)
upstream (fetch)
upstream (push)

Use the following command to add the upstream syndesis repository: git remote add upstream [email protected]:syndesisio/syndesis.git

With this in place, a --rebase performs the following steps:

  • Refresh upstream remote: git fetch upstream master
  • Try a git rebase upstream/master which rebases your current local working branch.
  • If this fails because you have uncommitted work:
    • A git stash is performed
    • The rebase is retried and should succeed
    • git stash pop brings back your changes. Stashing can fail with conflicts which you would have to resolve on your own.

Development Modes

The Syndesis application consists of a set of Docker images OpenShift resources descriptors for installing Syndesis. For development, minishift or CodeReady Containers are used, and most of the commands assume that you have either minishift or crc installed locally and executable directly from your path.

Minishift can be downloaded and installed from

Installation instructions for CodeReady Containers can be found in the project’s documentation.

For development OpenShift S2I builds and image streams are used. This mode works also when running with a real OpenShift cluster and is not restricted to Minishift or CodeReady Containers usage. The advantage is that a build automatically triggers a redeployment, so you don’t have to restart any pods manually.


All other options are specific to each command. You get a list of those options with syndesis <cmd> -h. These options are described in detail in the next sections.

The following commands are highlighted in this document:

buildUsed for building Syndesis and its various modules
uiStart the UI for local development
crcStart and install Syndesis on OCP4 CodeReady Containers
minishiftStart and install Syndesis on Minishift
installInstall Syndesis in a running cluster (other than Minishift or CodeReady Containers)
devUtility commands useful during development
releaseRelease Syndesis

If no command is given, build is the default. Remember a command must be the first argument, but there are additional possibilities to specify commands:

  • You can use the form --command anywhere as an option, too. E.g. using --minishift is the same as specifying “minishift” as the first argument.
  • A --mode command can be used, too (e.g. --mode ui)

The next sections describe the commands in detail. To add a new command, just drop a script file into $SYNDESIS_DIR/tools/bin/commands directory with following structure:


yourscriptname::description() {
    echo "Describe the command"

yourscriptname::usage() {
    cat <<EOT
    Describe the usage of the command

yourscriptname::run() {
    Do your stuff

syndesis build

The primary goal of syndesis build is to build Syndesis.

It is mainly a wrapper around Maven, Yarn and Go but adds some convenience functionality for common developer workflows.


A plain build command without any options performs a plain mvn install for all Java and UI modules. Plus it also builds the infrastructure operator via Go (see syndesis-build-operator for details)

This compiles all Java and Javascript artifacts and also runs all tests and code checks for the application modules.

You restrict the build to certain modules, which are divided into two categories: application modules which are the modules building up Syndesis. And infrastructure modules which help in managing the application itself.

You can individually select specific modules by using the --module (short: -m) option with a comma-separated list of modules, but there are also option to combine modules.

For example to build just the UI you can run:

$ syndesis build -m ui

The following modules are available:

serverMain backend providing a REST API for the user interface✔︎✔︎✔︎
uiThe SPA user interface application✔︎✔︎
metaMeta data and verifier used for verifying connections and providing connector metadata✔︎✔︎✔︎
connectorAll connectors used by Syndesis out of the box✔︎
integrationSupport libraries for running integrations✔︎
extensionTools for developing and running Syndesis custom extensions✔︎
commonCommon modules containing common code✔︎
s2iS2I base image used for building the runtime images✔︎✔︎
operatorInfrastructure operator for managing the application✔︎✔︎

All option ending with -images will also build the corresponding Docker image.

In addition to using top level modules that combine to a set of submodules you can also specify a very specific submodule using its groupId and/or artifactId. For instance the module name for the SQL connector module would be io.syndesis.connector:connector-sql or simply :connector-sql. In case you skip the groupId the leading colon in the module name is very important because this identifies the module to be a submodule rather that a top level module.

When you build individual modules you you can provide the option --image (short: -i) to create also the Docker image in the build, when the module is associated with a Docker image.

By default images are build via S2I against a running Minishift. This is the recommended way for developing as this automatically will trigger a redeployment after the build. However, for certain scenarios like when used in a CI system or when doing the release, the image creation can be done against are Docker daemon when the --docker is given. For this to work you must have access to Docker daemon, which you can verify with docker ps.

When the option --dependencies (short: -d) is given in addition to --modules, also all Maven modules which the specified modules depend on are build, too.


By default, all checks like license or code quality checks are performed. Also, all unit and local integration tests are run. A full build eats up quite some time, but you should always run at full blast before submitting a pull request.

However, to speed up the turnaround, several speed-up options are available. The following table shows these options, and also how long a full clean build over all modules takes: (but without building images)

noneDefault mode with all checks and tests
--skip-testsSkip all unit and local integration tests
--skip-checksSkip sanity checks like for correct license headers and
--flashFastest mode with skipping all checks and tests and with even some other aggressive optimizations

Maven mirror

At build time the dependencies are downloaded from maven central repository, it is recommended to install a local maven repository manager on your openshift to also serve as repository for the s2i builds running in openshift. If you want to have the local maven repository automatically created, you can specify the --maven-mirror parameter when installing minishift.

To build syndesis modules with the local maven mirror, use the --maven-mirror parameter, example:

$ syndesis build -m server -d -i -f --maven-mirror

Syndesis Operator

syndesis build can also build the infrastructure operator, which is a golang program.

You can build the operator by running syndesis build -m operator or as part of a module collection like --all-images or --infra-images

There are three modes, how the operator can be created:

  • Running you go compiler locally
  • Compiling in a local Docker daemon which allows volume mounts with the localhost
  • Compiling in Minishift Docker daemon, which was made accessible via eval $(minishift docker-env)

See below for the details.

Load dependencies

In any case, before you compile first you should use the option --ensure (short: -e) to setup the dependency tree. This will download all source dependency and cache them locally. To get rid of this cache, use the option --clean-cache.

If you compile for the first time, then --ensure will be added automatically.

Compiling locally

This is the fastest way for compiling the operator. Use the option --local (short: -l) for selecting the local compile mode.

It is also the recommended way when you are working on the operator. You project setup needs to fit however: The main project directory must be reachable as $GOPATH/src/ You can either move your project directory to this location or work with a symlink:

$ cd ~/Development/syndesis
$ mkdir -p $GOPATH/src/
$ cd ..
$ mv syndesis $GOPATH/src/
$ ln -s $GOPATH/src/ syndesis

By default this compiles into for your native architecture (amd64, darwin). When you use this mode with --image (short: -i) on macOS then go will be used as cross compiler so that the generated bimary can be used in a Linux image.

Compiling with a local Docker daemon

This is the default mode and is used also when doing the release. It use a builder image operator-builder which is created from the embedded Dockerfile in the install/operator/ script.

For this mode to work your Docker daemon must support volume mounts to the system from where you are calling syndesis. This is the case on Linux for locally installed Docker daemon and for Mac with Docker for Mac. It is not the case for Minishift which runs in a disconnected VM. But see below how you still can use Minishift for building.

go build with -mod=vendor will be run from this an ad-hoc container image (operator-builder), with your local directory mounted into the container so that the fetched dependencies can be cached in the local directories vendor so that the can be reused for the next run. Also the binary will be stored in your local directory, but this will alway be a Linux (amd64) binary.


Some common usage examples for syndesis build are

# Build all images (app and infrastructure) with S2I
$ syndesis build --all-images

# Create all application images and re-deploy Syndesis in the
# Openshift cluster, but do it as fast as possible. Don't build
# any golang code
$ syndesis build --app-images --flash

# Create the infrastructure operator by running go locally
# and calling dep ensure before
$ syndesis build -m operator --local --ensure

# Use a Camel snapshot for a clean build, build all modules
$ syndesis build --clean --camel-snapshot 2.21.0-SNAPSHOT

syndesis ui

Yarn is the package manager required to work on the project. It’s required to be installed, however the syndesis ui command can be used for day to day development tasks. For example:

# install all the dependendencies and build the project
$ syndesis ui --install --build
$ syndesis ui --serve --minishift

Runs the app in development mode using minishift. Automates running yarn watch:app:minishift and restores the console URL when you stop the development server. API calls will be proxied to the provided URL pointed by the BACKEND environment variable.

The proxy will require the session cookies to be able to properly work. The right cookies will be retrieved through an automated instance of Chromium, that will wait for the user to login. Once properly logged in - a condition recognized by the browser navigating back to the provided BACKEND URL - the session cookies will be extracted and the Chromium instance will be closed.

It’s also possibile to enable the chaos mode setting the CHAOS env variable. In chaos mode API requests have a 50% chance to fail with an error 500.
This mode is useful to test the resilience of the app.


  • the BACKEND URL should be the project URL as retrieved by Minishift/Openshift console.
  • doublecheck that the URL doesn’t end with a ‘/’.
  • never close the automated Chromium browser manually; if it stays open probably after a successful login something went wrong and should be debugged.

To run the tests use the --run-tests switch:

$ syndesis ui --run-tests

To run the test suite for a specific package you can pass the package name:

$ yarn test --scope @syndesis/package-name

syndesis crc

With syndesis crc you can adequately manage a CodeReady Containers installation for hosting Syndesis. This command is especially useful for a simple and self-contained development workflow.

When you’re deciding between CodeReady Containers and Minishift for local OpenShift development environment take note that Minishift supports OpenShift up to 3.11, and CodeReady Containers supports OpenShift 4.x onward. CodeReady Containers also requires more resources to run.

syndesis crc requires that you have a current crc binary in your path. You can download it directly from

syndesis crc will attempt to download the latest syndesis cli from the syndesis release page. If this fails, you can try downloading the right binary for your distribution and placing it under tools/bin/commands/binaries.


You can easily install Syndesis with the option --install. This option triggers the creation of all relevant OpenShift resources objects in the currently connected OpenShift project.

If you want to use a different project, then use --project (short: -p) to specify this project. We strongly recommend to use the project name syndesis, as the syndesis-operator uses it as default namespace.

Resetting CodeReady Containers

The quickest way to get a fresh Syndesis setup is to use --project which will install Syndesis into a clean, new project.

However, you can also recreate the whole CodeReady Containers installation with --reset. This will delete the CodeReady Containers VM (crc delete) and create a new one (crc start). It doesn’t harm if the CodeReady Containers VM does not exist so that you can use --reset also on a fresh CodeReady Containers installation.

If you want to get a real clean installation use --full-reset which deletes the ~/.crc directory which holds downloaded artifacts like the ISO image for the CodeReady Containers VM. Using --full-reset forces CodeReady Containers to re-download all those files.

There are several options which influence the re-creation of the VM:

--memoryMemory to use for the CodeReady VM.8 GB
--cpusNumber of CPUs used for the CodeReady VM.4
--pull-secret-fileFile holding the OCP4 pull secret
--vm-driverWhich virtual machine driver to use. For OS X this can be ‘virtualbox’
--bundlePath to system bundle (required when using virtualbox vm-driver)3.7.1


This short example performs the following actions: - Stops and deletes a running CodeReady Containers VM (if existent) - Removes ~/.crc (if existent) - Install Syndesis in OpenShift modes (S2I builds & image streams) in project syndesis - Opens Syndesis UI in the default browser

# Complete fresh installation in project "syndesis"
$ syndesis crc --full-reset --install --project syndesis

# Open Syndesis in default browser
$ syndesis crc -o

syndesis minishift

With syndesis minishift you can adequately manage a minishift installation for hosting Syndesis. This command is especially useful for a simple and self-contained development workflow.

When you’re deciding between CodeReady Containers and Minishift for local OpenShift development environment take note that Minishift supports OpenShift up to 3.11, and CodeReady Containers supports OpenShift 4.x onward. CodeReady Containers also requires more resources to run.

syndesis minishift requires that you have a current minishift in your path. You can download it directly from GitHub.


You can easily install Syndesis with the option --install. This option triggers the creation of all relevant OpenShift resources objects in the currently connected OpenShift project.

Setting a maven repository manager

To reduce build time, it is recommended to setup a local maven repository manager, you can use the --maven-mirror parameter when installing minishift, this it will install Nexus on the nexus OpenShift project.

Use the latest syndesis-operator

The syndesis-operator is an important part of syndesis, to update image streams, manage syndesis components in openshift and much more. The syndesis-operator is placed in $HOME/.syndesis/bin/syndesis-operator and then later installed in openshift. Use the -f parameter to download the latest syndesis-operator release.

Installing an addon

There are some additional software packaged as addon such as: jaeger, data virtualization, camel-k, knative, etc. You can install syndesis with these addons by using the --app-options parameter, for example, to install syndesis with camel-k:

syndesis minishift --install --project syndesis --app-options " --addons camelk"

Resetting Minishift

The quickest way to get a fresh Syndesis setup is to use --project which will install Syndesis into a clean, new project.

However, you can also recreate the whole Minishift installation with --reset. This will delete the Minishift VM (minishift delete) and create a new one (minishift start). It doesn’t harm if the Minishift VM does not exist so that you can use --reset also on a fresh Minishift installation.

If you want to get a real clean installation use --full-reset which deletes the ~/.minishift directory which holds downloaded artifacts like the ISO image for the Minishift VM. Using --full-reset forces Minishift to re-download all those files.

There are several options which influence the re-creation of the VM:

--memoryMemory to use for the Minishift VM.4 GB
--cpusNumber of CPUs used for the Minishift VM.2
--disk-sizeDisk space used for Minishift.20 GB
--show-logsWhether to show OpenShift logs during startup.false
--vm-driverWhich virtual machine driver to use. For OS X this can be ‘virtualbox’, ‘xhyve’ or ‘vmwarefusion’ (if installed).
--openshift-versionOpenShift version to use3.7.1


This short example performs the following actions:

  • Stops and deletes a running Minishift VM (if existent)
  • Removes ~/.minishift (if existent)
  • Install Syndesis in OpenShift modes (S2I builds & image streams) in project syndesis
  • Open Syndesis UI in the default browser
  • Install a Nexus maven repository manager in project nexus

    # Complete fresh installation in project "syndesis"
    $ syndesis minishift --full-reset --install --project syndesis --maven-mirror
    # Open Syndesis in default browser
    $ syndesis minishift -o

syndesis dev

Dev commands are useful helpers for developing Syndesis

Debug a syndesis component

The --debug parameter enable port-forwarding of port 5005 from a specific pod (by default: “server”) to port 5005 on the localhost. You then can point your Java IDE to port 5005 on localhost for connecting for remote debugging. As argument to --debug “server”, “meta” and “atlasmap” can be used, which are our Java based services. For this to work the running pod must have been started with java debug agent enabled. You can enable it by setting the environment variabel JAVA_DEBUG=true to the deployment config, for example, the following command will enable java debug agent in the syndesis-server deployment config and the pod will be restarted.

oc set env dc/syndesis-server JAVA_DEBUG=true

Prune old stuff

As the syndesis components are updated or integrations installed, after days or weeks many old syndesis components such as images, deployment configs, builds are stored and consumes space, it may slow the system down. So, you can free space by pruning old stuff from openshift by using the --cleanup parameter.

Install Maven Nexus as mirror

The Syndesis S2i builds are loading dependencies from Maven central respectively Red Hat repositories. In order to improve performance and save some bits in transfer we recommend to use a Maven Nexus as mirror. This will decrease the amount of bits loaded from the internet every time a Syndesis integration is created.

You can add the Maven Nexus application in a separate project namespace to the OpenShift cluster by using:

$ syndesis dev --install-maven-mirror

This will create a new project on the cluster nexus and will install the latest Nexus Maven repository manager. You can use this Nexus instance when building and pushing new images to the Syndesis image streams using S2i.

$ syndesis -m s2i -i --maven-mirror http://nexus-nexus.apps-crc.testing/nexus/content/groups/public

This will build a new base S2i image and use the Maven Nexus as mirror so all previously loaded dependencies will be loaded from the local Nexus instance instead of loading from the internet.

syndesis release

Use syndesis release for performing a release of Syndesis. A Syndesis release consists of:

  • Maven artifacts of the backend and runtime services
  • Docker images pushed to Docker Hub
  • Manifests created for

This chapter describes how you can efficiently perform a release and how to troubleshoot if something goes wrong. This documentation might also be interesting to you even when you do not perform a release on your own, as it might help you to understand how the various Syndesis artifacts fit together.

Even though the documenation mentions how to do this manually, we usually perform an automated release on our CI server. The CI server is set up with the necessary credentials and anyone with the permissions to run the release jobs can run a release.

A lot of output is produced during a release. If you are only interested to see the major steps only, then you can use --log to redirect the output to a specific log file. This log file will contain all output (and if you add --verbose you see even more output), but on the console you will only see the current step that is actually performed.


An example run for a dry run for 1.3.1 release on the current branch look like:

./tools/bin/syndesis release \           1
    --release-version 1.3.1 \            2
    --local-maven-repo /tmp/clean-repo \ 3
    --log /tmp/build.log \               4
    --dry-run                            5
  1. Always run syndesis from the repo and branch you want to release.
  2. The release version is mandatory and must be in the format <major>.<minor>.<patch>.
  3. Use a clean local Maven repository to avoid side effects
  4. Redirect the full output to /tmp/build.log but still print the main steps to the console.
  5. Make only a dry run, without pushing any artifacts out nor checking in any changed files.


To perform a release, certain preconditions need to be given.

First of all, you need to have access to the various systems to which release artifacts are uploaded:

  • You need to be logged in to Docker Hub and your account needs to have write access to the syndesis Docker Hub organisation.
  • You have gpg to have installed and set up a gpg-agent for being able to sign Maven artifacts during deployment in a non-interactive mode.
  • You need to have access to the “syndesis” account on ( for being able to publish Maven artifacts. This credential needs to be added to either your ~/.m2/settings.xml or you can use an settings file with the --settings-xml option. The credential needs to be added to the server with the id oss-sonatype-staging.

You have to perform the release from a locally checked out Syndesis repository, which can be either checkout from a branch like 1.2.x for a patch release or directly from master. It is highly recommended to run the release directly from a freshly checked out directory:

# Go to a temporary directory
$ cd /tmp

# Clone repository afresh, but only use the last history entry (--depth=1)
$ git clone --depth=1

# Jump into the directory
$ cd syndesis

# Switch to the target branch if needed (or stay on master)
$ git fetch --depth 1 origin 1.2.x:1.2.x
$ git checkout 1.2.x

# Call Syndesis from the checked out clone
$ ./tools/bin/syndesis release --release-version 1.2.8 .....

# Push to origin after a successful release.
# This automatically done if --no-git-push is given
$ git push 1.2.8
$ git push -f 1.2

# Remove the temporary clone again
$ cd ..
$ rm -rf syndesis

Please note that you should always call syndesis out of the branch for which the release is for. If there is an issue due to bugs in the release script itself, please fix them on the branch with the usual developer process (i.e. opening a PR request). syndesis release must always work for the branch where this script is, too.

Release steps

A release consist of several different steps, which can be grouped into two groups:

  • Build steps are performed to build the release and create the artifacts. Also during the build Maven artifacts are uploaded to the staging area for publishing to Maven central
  • Persist steps are then used for releasing objects, pushing Docker images to Docker Hub, committing and tagging in Git (but only when the build steps have been performed successfully).

Build steps

  • Check whether the current local Git clone is clean, i.e. that is does not have any modified files. The script will abort if this is the case.
  • Update the versions of all pom.xml files below app/ to the version given with --release-version. If no --release-version is given, then the script aborts.
  • Run an mvn clean install to verify that the build is not broken and all tests succeed.
  • Run an mvn -Prelease clean deploy to deploy all artifacts to a new staging repository on, the platform for release artifacts on Maven central. The staging repository on this Sonatype Nexus is validated and closed.
  • If --docker-user and --docker-password is given, then a docker login is performed. Otherwise, it is assumed that the user is already logged in.
  • The Docker images are created with mvn -Prelease,image package in the server, meta, ui operator, and s2i modules.

If the option --dry-run (short: -n) is provided, the script drops the staging repository at Sonatype and stops. You should examine the generated files and before starting a real build, reset the repository (git reset --hard).

The builds are using a clean local Maven repository, which otherwise is usually taken from ~/.m2/repository. This new local cache should ensure that we have a completely fresh build without interference from previous builds store in the local Maven cache in the home directory. You can provide such a directory with --local-maven-repo which will be taken directly (so it’s good if you have to perform multiple runs like with --dry-run). If not provided, a new temporary directory is created and also deleted after the release run.

Persist Steps

  • Push Docker images to Docker Hub. In addition to the images that carry the full release version as the tag, also a tag for the minor version is attached and pushed. E.g. when the release version is 1.2.8, then the minor version is 1.2. If this minor version tag already exists on Docker Hub, its moved to the newly created version.
  • The staging repository on Sonatype is released. It will take a bit, but the artifact should then be downloadable from Maven central soon after.
  • Commit all modified local files to the local Git repo.
  • Create a Git tag for the release version (e.g. git tag 1.2.8).

The next steps are for creating templates for the minor version:

  • In install create new templates which contain image streams that reference images with the minor version (e.g. syndesis/syndesis-server:1.3 for a release version of 1.3.8).
  • Commit those generated templates
  • Tag it with the minor version (e.g. 1.2), overwriting an already existing minor version tag

Next, we are switching back to the next development version of the pom.xml files. This version can be given with --dev-version, but by default, it is calculated automatically as <minor.version>-SNAPSHOT (e.g. 1.2-SNAPSHOT). This new version is then committed to the local git repository.

Finally, the tags just created on the local Git repo is pushed to the remote repository. You can omit this with the option --no-git-push. If to so, the last step can also be performed manually afterwards with:

$ git push 1.2.8   
$ git push -f 1.2   1

NOTE: The usage of -f flag as the minor tag needs to be moved.

Please be careful to not push the master branch upstream (i.e. do not a plain git push). We only want to have the tag with all the release preparation steps, not on the branch so that pull requests can be still be easily rebased with out conflict because of the temporary version changes.

Minor Version Templates

What is now the thing with this minor version? Why is the needed and how does it work?

Syndesis follows a semantic versioning approach. So, patch level releases (i.e. all releases which only change the last digit in 1.2.8) are fully compatible with all other patch level versions. In order to allow easy bug fix upgrades, we also create a tag which contains only the version parts up to the minor version (e.g. 1.2). These tags always points to the latest full version of its minor version. If, e.g. 1.2.8 is the latest 1.2.x version, then the tag 1.2 point to this 1.2.8 version. Corresponding to these Docker image variants, there exist two OpenShift templates variants:

  • One set of templates directly references the Docker images which its full version, e.g. syndesis/syndesis-ui:1.2.8. Applying such a template will keep your application at precisely this patch-level. You would have to update your templates and recreate your applications if you want to upgrade.
  • The other set of templates references images only via its minor version, e.g. syndesis/syndesis-ui:1.2. Using these templates has the advantage that application created from these templates automatically benefit from patch releases. The templates contain an image change trigger which will redeploy the application if the images change. So when we release the next patch level release, moving the minor version tag to this patch level release, then the application gets automatically redeployed, and it will pick up the new image.

These two sets of templates can be reached directly from GitHub as the git tags correspond to the Docker tags (i.e. a 1.2.8 tag and a 1.2 tag which will be moved forward).

Snapshot Release

With the option --snapshot-release a lightweight snapshot release for the images and templates can be created. The tag/version is calculated automatically by picking up the latest release number (e.g. 1.3.5), increasing the patch-level by one and adding a daily timestamp (e.g. 1.3.6-20180419). According to Semantic Versioning 2.0 this is considered to be a version larger than 1.3.5 but smaller than 1.3.6.

This tag can be referenced to in syndesis install and syndesis minishift.

In detail, a snapshot release differs from a normal release as it:

  • …​ doesn’t release artifacts on Maven central, but pushes Docker images and creates a Git tag for referencing the proper templates.
  • …​ skips all checks and tests when building to maximise the likelihood that the release succeeds. The rationale here is to better have untested daily snapshot release than no snapshot release because of test failure (which in many cases are not because of errors, but of failure in the infrastructure)
  • …​ force pushes the snapshot tag on GitHub so that multiple releases per day are allowed


$ syndesis release \
     --snapshot-release \                   1
     --local-maven-repo /tmp/clean-repo \   2
     --git-remote origin \                  3
     --docker-user "${DOCKER_USER}" \       4
     --docker-password "${DOCKER_PASSWORD}"
  1. Enable snapshot release with a version in the format 1.3.5-20180419
  2. Point to an empty repository to avoid side effects when building
  3. Push to the origin repository
  4. Docker credentials required for pushing to Docker Hub

A daily Jenkins job with this configuration run on for creating a daily snapshots.


When you run the syndesis release command and when it should not succeed, you might have to perform some cleanup steps yourself (there is now automatic rollback). However, care has been taken to move all persistent changes to the end of the release flow, so if something breaks early, you only need to clean up locally. If the process fails before the step === Pushing Docker images you only need to:

  • Reset your local git repo with git reset --hard
  • Potentially remove the create staging repository on (but it doesn’t harm if it is not cleaned up immediately).

After pushing the Docker images, it should be improbable that things go wrong. But these things should take care of if this should be the case:

  • Remove Docker Hub tags for the pushed images, which is best done on the Docker Hub Web UI
  • Revert your local git commits to the point before the release. If you did this on a fresh checked out repo (as recommended), you just could delete the whole clone.

syndesis install

With syndesis install you can install Syndesis to an arbitrary OpenShift cluster. If you want to install to Minishift the syndesis minishift command is recommended as it supports some additional features specific to Minishift.

The deployment happens to the currently connected OpenShift cluster. So it’s mandatory that you have logged into the cluster with oc login before. You can check the status with oc status.

The installation process consists of two steps:

  • An initial setup which has to be performed as cluster admin which is a one-off action which needs to be done only once.
  • Installation of Syndesis into a specific project by the app admin, a regular user of OpenShiftm which can be performed as many times as required.

Initial Setup

In the initial setup, you have to register the custom resource definition (CRD) to allow to deploy Syndesis resources. This step has to be performed by the admin.

Also, if you want to allow an OpenShift user to install Syndesis on her own, then you have to grant specific permissions to her.

To perform this setup step, which needs to be performed only once per cluster, you have to run syndesis while being connected as a cluster admin. For minishift use oc login -u system:admin if you have the admin-user addon enabled, for crc follow the login instructions you got when starting up crc.

$ syndesis install --setup

This will install only the CRD. In addition to grant a user developer the proper permission to create a Syndesis resource, you should add --grant <user>:

$ syndesis install --setup --grant <user>

This call adds permissions to read and write Syndesis resource objects for the current project. If you would instead want to allow the user managing Syndesis resources in the whole cluster, you should add a --cluster. This cluster-wide access is especially required when you plan to use the --project option to use a new project or recreate the existing one, as in this case the role association to this project gets lost.

Installing Syndesis

After the CRDs a registered, you can easily install Syndesis directly with

$ syndesis install

Depending on whether you have granted the current user access this step has to be done either as admin or as a regular user.

Example for Minishift

# Enable the admin user on Minishift
$ minishift addons enable admin-user

# Create a minishift instance
$ minishift start --memory 4192

# Switch to admin
$ oc login -u system:admin

# Register CRD and grant permissions to "developer"
$ syndesis install --setup --grant developer --cluster

# Switch to account developer
$ oc login -u developer

# Install Syndesis
$ syndesis install

A route name can be given with --route. This step can be omitted as the operator can autodetect the route. If you provide the route manually, you need to check your OpenShift installation. Typically the route name is the name of your OpenShift project followed by the cluster’s hostname. E.g. a route --route is specific to the Fuse Ignite test cluster and for the project proj186023. However, you don’t have to provide the route name.

If you want to have a link to the OpenShift console to read the Pod logs, you have to add the --console option with the full URL to the console. If not given, no link appears.

By default, this commands installs Syndesis in the currently connected project, but you can specify an alternative project with --project <project>. If this project already exists, it gets deleted unconditionally before the deployment, so be careful when using this option. By default, you are asked whether you want to delete the project for recreation. You can switch off the security question with the option --yes (short: -y).

If you want to wait until everything is running (including fetching of the Docker images), you can specify --watch (short: -w) which blocks the script until everything is set up.

You can also automatically open Syndesis in the browser after the installation with --open (short: -o)

Development Mode

As with syndesis crc or syndesis minishift you can also use this command to set up a development platform for Syndesis. Development platform here means that you can create Docker images on your own with syndesis build and can use them with an automatic redeployment after the build.

You can switch on this mode with the option --dev. When the operator has deployed the application, the application imagestreams refer to Docker images pushed to Docker Hub. To change the imagestream references to the images built with syndesis build --all-images, these imagestreams needs to be patched after the initial images have been fetched from Docker Hub. If you use the --dev option, then this update is done automatically.

Selecting the Version

With the option --tag you can select a specific version of Syndesis to install. By default, the currently checked out checked out branch is used.


$ syndesis install --route --tag 1.4

This example installs the latest Syndesis version of the 1.4 branch to the local cluster.

You can see a list of available tags with git tag. Tags prefixed with fuse-ignite are suited for the Fuse Online cluster as those templates do not contain images streams themselves but refer to the image streams installed on this cluster.