simplify the Pipeline choices for maven projects

[jstrachan]

e.g. should we just have a 'Developer build' pipeline that literally only does mvn fabric8:deploy or should we just default a single Jenkinsfiles which can do developer build, CI/PRs and CD?

Then just have a configuration option to swizzle them between dev build to real CI / CD?

[rawlingsj]

we have a maven CI function that does that https://github.com/fabric8io/fabric8-pipeline-library/blob/master/vars/mavenCI.groovy#L17

and used in a jenkinsfile here https://github.com/fabric8io/fabric8-jenkinsfile-library/blob/master/maven/CanaryReleaseAndStage/Jenkinsfile#L30-L34

is this the same idea?