Recently we changed our way of building branches. We use GIT and have scm polling to build branches. First, we used to poll a specific branch name (release/1.0). Now we use a regex (release/*). For example, instead of having:
jenkinsJob1 that builds branch release/1.0 jenkinsJob2 that builds branch release/2.0 Now we only have one job: jenkinsJob that builds release/* (so release/1.0 and release/2.0 are both built by job) However, the new commits don’t show as changes anymore (when I click changes summary is blank). It now only shows revision and branch name when clicking on build number. This causes our developers to get confused because they're used to seeing their commit messages. I assume this behavior is because the previous build was built from different branch and so it can’t aggregate changes. Is this the case and is there a workaround? 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4e729e15-2c84-453a-a9e1-3c49619572ce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
