No, I'm talking about my plugin email-ext. There was a different build result on buildhive than jenkins.ci. This has been the case on a couple of occasions.
On Thu, Oct 10, 2013 at 8:12 AM, Jesse Glick <jgl...@cloudbees.com> wrote: > On Thu, Oct 10, 2013 at 12:56 AM, Slide <slide.o....@gmail.com> wrote: > > Is there a reason that plugins are built on both? What is the purpose of > having both? > > BuildHive runs older software and uses inferior hardware, so > jenkins.ci is preferred where possible. However only BuildHive is > currently set up to build pull requests (with the exception of core). > At some point of course there should be some kind of consolidation, > but no one from CloudBees has had time to work on it so far. > > If you are talking about maven-plugin, its tests seem unreliable, > which ought to be fixed at the source level; any help with diagnosing > and correcting the tests which fail only on CI servers would be much > appreciated. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- Website: http://earl-of-code.com -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
