release. It arrives
about once every three months and remains stable for those three months.
Mark Waite
--
*From:* KP koen.pollent...@gmail.com
*To:* jenkinsci-users@googlegroups.com
*Sent:* Thursday, November 8, 2012 2:02 AM
*Subject:* Re: Jenkins failed to record
Exactly the same issue, but with (old built-in 1.x) CVS plugin.
Issue went away after revert tot 1.488.
After the lazy loading problem made jenkins unusable, now this... It seems
the stability of the jenkins updates is getting very bad lately. 2 bugs
completely breaking jenkins, only in a
, 2012 2:02 AM
Subject: Re: Jenkins failed to record SCM polling
Exactly the same issue, but with (old built-in 1.x) CVS plugin.
Issue went away after revert tot 1.488.
After the lazy loading problem made jenkins unusable, now this... It seems the
stability of the jenkins updates is getting
The problem gone away after I downgraded Jenkins to 1.488.
On Tue, Nov 6, 2012 at 5:20 PM, Dirk Kuypers kuypers.d...@gmail.com wrote:
just vote for:
https://issues.jenkins-ci.org/browse/JENKINS-15718
BR
Dirk
2012/11/6 hezjing hezj...@gmail.com
I made the conclusion too early, the
I made the conclusion too early, the problem is still there.
The mercurial plugin is able to poll the changes for the 1st time, e.g.
when the workspace directory is deleted. Then, it fails in the subsequent
polling, e.g. when the workspace directory is created.
On Tue, Nov 6, 2012 at 11:33 AM,