Ahh yes I remember that build now... dear me... there were nightmares for a
few weeks from having peeked at the poms
On 22 July 2014 13:46, Jesse Glick wrote:
> On 22 July 2014 09:00, Igor Fedorenko wrote:
> > Unfortunately, MNG-5312 didn't have any
> > test case so I am wondering if Jesse or
On 22 July 2014 09:00, Igor Fedorenko wrote:
> Unfortunately, MNG-5312 didn't have any
> test case so I am wondering if Jesse or somebody else can provide more
> details about exact conditions that triggered MNG-5312 and, ideally,
> setup a regression test.
As noted in MNG-5312, I was able to rep
BCC'ing Jesse in case he's not monitoring this list.
The exact conditions were related to the [evil job type](
http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html)
and I think the test case was within
https://github.com/jenkinsci/maven-plugin or perhaps a specific
I am trying to assess potential impact of a performance regression on
the current master. I believe the problem has to do with inconsistent
caching of ModelData instances and is similar/related to MNG-5312 [1]
that was fixed back in 2012. Unfortunately, MNG-5312 didn't have any
test case so I am w
