search

IBM-Cloud / logistics-wizard-toolchain

Toolchain configuration files for the logistics-wizard demo
13 stars 15 forks source link

Investigate splitting the Delivery Pipeline in two to build master and dev separately #14

Closed l2fprod closed 7 years ago

l2fprod commented 7 years ago

The current Delivery Pipeline builds the dev and the master branches. However there is no link between the two as they both build from the source in Git.

A typical pipeline would look like: [DEV-BUILD] -> [DEV-DEPLOY] -> [BUILD] -> [DEPLOY] which creates confusion as it makes it sound like DEV-DEPLOY triggers BUILD.

An option would be to create one delivery pipeline per branch, each with its own "build & deploy" flow. It should be easier to understand and more scalable if one wants to add a pipeline for a new branch as example.

Aim of this issue is to try this approach on the logistics-controller module as example to understand the impact.

l2fprod commented 7 years ago

changed the webui in https://github.com/IBM-Bluemix/logistics-wizard-toolchain/tree/split-dev-and-master

image

multiple pipelines work as expected. all builds are started.

however we might need to use a shorter name for the pipeline so that DEV and PROD labels are visible.

also given we create more pipelines than repositories we have more "deliver" than "think" or "code" boxes so there is no horizontal alignment - there was before but this was not by design.

l2fprod commented 7 years ago

split all pipelines

image

rvennam commented 7 years ago

Much better!

rvennam commented 7 years ago

merged with #16