Build and Distribute your Ionic apps using Greenhouse CI & Relution

A smooth and stress-free workflow that you can explore right now. For free! Learn how to build and distribute your Ionic app that you’ve set up with Generator-M-Ionic. Build your app in the cloud using Greenhouse CI and deliver them straight to your colleagues’ and customers’ devices with Relution! For every push to your repository you app will be built and published, making it available to everyone who needs it by a simple button press!


What you need:

  1. A working Generator-M-Ionic project
  2. Relution Account – the free subscription suffices
  3. Greenhouse CI Account – free plan is plenty here as well

In your browser: create an account for Relution on [](

Prepare your project

There’s three alternatives here:

  • Demo project: Use the Generator-M-Ionic Demo project on Github for now. You’ll just need to copy the URL, no cloning with Git or anything:
  • New project: Setup your own Generator-M-Ionic project. Checkout the documentation to get started.
  • Existing project: Use an existing project that you’ve set up with Generator-M-Ionic. It needs to be in a repository that is available on the web.

In any case your Generator-M-Ionic project needs the build script. The demo project already contains this, so if you chose to build the demo project, you’ll have to do nothing. If you create a new project however, you need to select the Greenhouse & Relution option in the Ecosystems Question. And for your existing project you can run the greenhouse sub-generator which will generate the for you:

yo m-ionic:greenhouse

Reading the Generator-M-Ionic Continuous Integration Guide sheds some light on the‘s functioning. However it is not necessary to understand that in order to proceed.

Build your app in Greenhouse

After you’ve prepared your project, created your Relution and Greenhouse accounts and signed into and using your browser, you can now create a new app in Greenhouse.

Create a new Greenhouse app

In the Greenhouse project overview, add a new app by clicking the add a new app button.

In your browser: create a new app on [](

Once you’ve done that, supply the URL to the repository you want to build as part of the initial project configuration as seen below. The URL for the Generator-M-Ionic Demo project is

Greenhouse CI: initial project configuration for your new app

Alternatively if you want to build your own project provide any other URL to a public repository or even add your private repository using SSH or Basic Auth. As long as your repository contains a project which was set up with Generator-M-Ionic this guide is right for you. For building other projects follow the Greenhouse CI Documentation.

Configure Greenhouse Environment

When you hit continue, the setup will jump right to the Build configuration. Navigate back to Environment. This part is needed to tell Greenhouse how to prepare and build your Generator-M-Ionic app by uploading the file of your project. If you’re interested on what exactly the does, read the Generator-M-Ionic Continuous Integration Guide.

Greenhouse CI: go back to `Environment`

Click the add button under Environment Files:

Greenhouse CI: add an environment file

Select or drag and drop the file of your project:

Greenhouse CI: upload ``



Configure Greenhouse Build

Now that we told the Greenhouse CI how to prepare your project for building by providing the script of your project, we can now continue and configure the actual Build.

First select the branch of your repository that you want to build.

Greenhouse CI: Build Configuration – Select Branch

Greenhouse will then proceed to prepare and discover your project. This might take a while, because it will clone your project, checkout the branch and perform a complete npm installbower install and a first gulp build to discover which platforms you’re building for.

When this is finished you’ll be able to complete your build configuration. If you’re building for iOS, you will have to upload your provisioning profile as well as signing certificate along with its password.

Need help with the provisioning profile and the signing certificate?

Greenhouse CI: Build Configuration – Complete configuration

Hitting save will trigger the first full build of your app which will produce the .ipa and .apk files of your app for iOS and Android respectively.


You’ll be navigated back to the project overview. Pressing View build on your project will take you to an overview of your builds for that project.

Greenhouse CI: Project overview – building

For now there’s only one build, because you just started your very first complete build.

Greenhouse CI: Build overview

By clicking on it you can see details of your build as well as a live log of the actions that are currently being performed.

Greenhouse CI: Building – live log

Now that your project has finished building you can download your build artefacts containing the .ipa and .apk files from the Overview tab.

Greenhouse CI: Building – download build artefacts

Manually connecting and installing the apps on the devices is a little cumbersome and mostly not desirable. With Relution distributing your app to everybody who needs it and installing it is only a button press away.

Publishing to Relution

In order to configure your app for distribution with Relution, head back to your project’s overview and press that little gear icon towards the top-right.

Greenhouse CI: Project overview, configure via gear icon

You’ll be taken to the project configuration that you know from earlier. Go to the previously unavailable Publishingsection and select Relution. Provide your username, password -this was sent to you via email- and the Relution Server URL: Then hit save!

Greenhouse CI: Project overview, configure via gear icon

Go back to your project’s overview and hit the Build button.

Greenhouse CI: Project overview, build!

This will start building your app just as before. Only at the end it will no publish your app to Relution making it easily available for testing and delivery purposes! You can see that your build is being published to Relution at the end of the live log of your build.

Greenhouse CI: publishing to Relution

When you log into using your browser and then navigate to Apps > App Store, you’ll find the Android and iOS apps you just built.

Greenhouse CI: publishing to Relution

The only thing left to do now, is to get your app on your devices. The Relution app comes to the rescue.

Install your app via the Relution app

The Relution app is found in the Android Play Store and the iOS App Store and you can think of it as your own personal app store for managing apps.

Install the Relution app

After you’ve installed it, login using your credentials.

Relution app: login

Using the side menu, navigate to the Development section.

Relution app: menu

This contains all your apps that are currently in the Development stage. In our case, this is only the one we just built.

Relution app: apps in Development

And tada! Your app is ready to be used on your device!

Relution app: your app was installed

New versions of your app

Now every time code changes are pushed to the master branch of your repository, Greenhouse will fully build your app, publish it to Relution and from there it is delivered straight to everybody’s device. Opening the Relution app and installing the new version is the only thing left to do.

With Relution you can register different devices and different users to your organization and assign them different roles so they can see different apps at different stages. For instance apps in Development are only visible to the development team until they approve a specific version for Review by other stakeholders, who can then in turn approve the app which will move that app to Production and make it available for the end-users.


For further information on how to use Relution, head over to the documentation and in order to learn more about how to use the Greenhouse CI head over to their documentation on


Granted, the Greenhouse CI integration for Generator-M-Ionic project is a little time-consuming at times and not ideal yet, but it works for now. Nevertheless we’re looking to improve the whole process and make it more slick! Feedback is very welcome!

Also published on Medium.

Leave a Reply

Your email address will not be published. Required fields are marked *