How do you normally handle branches and merging? I use the same tools and branching and merging rules as the rest of the team, i.e. development and QA.
In our case, the teams are required to merge from master to their project branches on a regular basis, so they will eventually get my changes that I make in master. On Tuesday, July 21, 2020 at 5:37:39 PM UTC-4, Martin Schmude wrote: > > Dear all, > > if I understand multibranch jobs right, then a Jenkinsfile in branch > "master" will be replicated into all other branches drawn from "master". > It has to be like that because the Jenkinsfile is the "marker" that tells > Jenkins to build a branch, and how to do that. Branches without a > Jenkinsfile will not be built. > > This will often result in code duplication, with all the well-known issues. > If a small change has to be made to the Jenkinsfile, it has to be applied > to all branches. > > How do you handle that issue? Is there a recommended practice? > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/26c8d410-37d8-4de5-8b7b-1b8bdeab9baao%40googlegroups.com.
