Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

simplify the Pipeline choices for maven projects #9

Open
jstrachan opened this issue Mar 7, 2017 · 1 comment
Open

simplify the Pipeline choices for maven projects #9

jstrachan opened this issue Mar 7, 2017 · 1 comment

Comments

@jstrachan
Copy link
Contributor

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
Copy link
Contributor

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

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

is this the same idea?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jstrachan @rawlingsj