Contains project quickstarters (boilerplates) for Spring Boot, Node.js, React, R Shiny - all including CI/CD integration & Jenkins build slaves
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
jenkins-slaves Update version of xvfb Feb 8, 2019
ocp-templates Merge pull request #103 from BIX-Digital/feature/BIX-511-waf-api-gate… Jan 11, 2019
.gitignore Initial Commit Jul 27, 2018
LICENSE Update changelog Jan 25, 2019
logfile Task/add gradle into slave (#23) Aug 13, 2018


This repository contains quickstarters, which are basically templates that help to start out with a component quickly. Available components include e.g. Spring Boot, Akka or Angular.


The quickstarters are not used directly, but triggered via the provisioning app, which in turn triggers a job in Rundeck (defined in rundeck folder), which then uses the files in this repository.


As the quickstarters are triggered via Rundeck, the changes need to be on the production branch in order to be "live". It is possible however to mimick what Rundeck does locally.

The general procedure is:

  1. Clone the repository
  2. Go into a quickstarter folder, e.g. be-node-express
  3. Run
  4. Run
  5. Run from the root of the repository
  6. Run from the root of the repository

Note that those scripts might need parameters to work, and often need to be adjusted slightly to work (e.g. removing chowning to rundeck user).

Upgrade an existing GIT repository to ODS

Push your repository into the newly created bitbucket project (and note the name of the repo & project)

Logon to rundeck and pick the common/prepare-continuous-integration rundeck job

  1. Pick the technology target thru component type - this will ensure you get the right jenkins file based on the technology you pick - and should fit the technology you have built your application with
  2. Provide quickstarter_directory - this can be any filesystem directory - usually in /tmp/<component name> where the git repository will be cloned to
  3. Provide project_id - this is the project name you noted in step (0)
  4. Provide component_id- this is the name of the component (from step 0) that will be rendered into the jenkins template, and also used as name for the openshift resources
  5. Provide git_url_http/ssh - this is the URL to clone and commit to for the job.