I've seen inconsistent results from the "Recent Changes" links on my various Jenkins jobs which use the Git plugin 2.0 beta.
One of the jobs stopped showing history, even though I know the changes were arriving because that job was merging them and pushing the merge results to the central repository. One of the jobs shows only the most recent change, not the changes which preceded it. Most of the jobs show the expected set of changes as they did before the upgrade to the Git plugin 2.0 beta. Unfortunately, I don't have a way to duplicate the problem and don't have any obvious differences between the jobs which are behaving as expected and hte jobs which are not behaving as expected. Mark Waite On Thursday, July 25, 2013 4:40:36 PM UTC-6, Kohsuke Kawaguchi wrote: > > > Hi, > > We've been working on a major improvement on Git plugin, and it's now at > the point that it's ready for general consumption. > > As Git plugin is used by many and we want to reduce the chance of > regressions, I'm calling for people to try out this unreleased Git 2.0 > plugin. > > Please see [1] for the new features and how to try this out on your own > instance. Looking forward to hearing the feedbacks. > > > [1] > https://wiki.jenkins-ci.org/display/JENKINS/Git+plugin+2.0+beta+testing > -- > Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ > Try Jenkins Enterprise, our professional version of Jenkins > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
