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.

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

time boxed releases versus release on master merge #11

Open
jstrachan opened this issue Mar 7, 2017 · 0 comments
Open

time boxed releases versus release on master merge #11

jstrachan opened this issue Mar 7, 2017 · 0 comments

Comments

@jstrachan
Copy link
Contributor

this relates a little to this issue: #10

what if folks want to move to a time boxed release approach; so that merges to master just do a developer build (so a mvn fabric8:deploy in some namespace); then later on they trigger a CD release via a separate pipeline?

So we'd want a developer pipeline for master; then a Jenkins job folks can trigger to do a release when they choose to do.

How should we configure/record that? As we'd want 2 Jenkins jobs really - one for master and one for 'time boxed releases'?

Maybe the simplest approach for this use case is to create a release branch with a Jenkinsfile which runs the CD release pipeline - from the master branch (so you never need to really edit the release branch unless you wanna edit the release pipeline)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant