lets add the ability to use the current branch name to decide if we do a full release, CI job or developer build

[jstrachan]

we could use branch names and naming conventions/patterns to decide which branches are

• production release branches (where each release creates a new real release version number, artifacts and docker image
• CI or PR jobs (where unit tests are ran, maybe a local snapshot image is built and tested locally but nothing is pushed for realz)
• a developer editing branch - where a developer image is updated and used in a developer namespace (so each change is running quickly in a users namespace) to give a kinda RAD editing environment

We could use variables to define the patterns used to differentiate between the kinds of builds. e.g. branches called master or starting with release could be the default production releases; branches starting with editing- could be developer editing branches and anything else assumed to be CI / PR branches?

Then if folks fork a master branch, they get a new CI build for the changes they push

[jstrachan]

I wonder if we should configure which branches are releases + which are PRs / feature branches / issue branches (for CI) - and which are 'developer branches' (for continuous testing + fast running) in the ConfigMap.

That'd also avoid some possible security issues changing the Jenkinsfile in a PR etc