-
Notifications
You must be signed in to change notification settings - Fork 9
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
Branching strategy #67
Comments
the new pipeline format will have something similar too (after the api refactor). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following the jenkinsfile example, we need to define a way to handle branches, after a long discussion/argument over the same solution, @madziefe and I came up with something like this:
So far, we think this is a flexible way of handling branches. basically when a build is created, the multi-branch part will get parsed and the actual list of stages will be added to pipeline. the
default**
means it's the behaviour if no branch is matched.The text was updated successfully, but these errors were encountered: