I know this has been brought up at least once before several years ago, but with time and the advent of Pipeline, I am wondering if best practices have changed. I am looking at automating releasing of Gitflow projects. Most of our projects have been stored in Subversion and we use the Maven Release Plugin which takes trunk, and tags it for release. Gitflow releasing is significantly more involved with a release branch being created and multiple (potentially error-prone) merges required. It seems like many of those deeply involved with Gitflow do not do CI/CD.
Is there any advice or best practices for providing automated release processes for Git Flow? Thanks. -- 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/171e6801-0d1b-4013-be2f-94e311907938%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
