• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: core
• Labels:

  None
• Environment:

  Win2003 R2 32bit, JDK 1.6.0_18, Tomcat 6.0.20, Hudson 1.350, Subversion plugin 1.13

[JENKINS-5926] builds (SCM polling based) are triggered even when there are no (SVN) SCM changes

Collapse comment: Anne Stellingwerf added a comment - 2010-03-13 05:47, Edited by Anne Stellingwerf - 2010-03-19 03:38

Anne Stellingwerf added a comment - 2010-03-13 05:47 - edited

I've got the same issue, but then on

WinXP Pro (Dutch) 32bit, running Hudson as a service, JDK 1.6.0_18, Hudson 1.349, Subversion plugin 1.13

Expand comment: Anne Stellingwerf added a comment - 2010-03-13 05:47, Edited by Anne Stellingwerf - 2010-03-19 03:38

Anne Stellingwerf added a comment - 2010-03-13 05:47 - edited I've got the same issue, but then on WinXP Pro (Dutch) 32bit, running Hudson as a service, JDK 1.6.0_18, Hudson 1.349, Subversion plugin 1.13

Collapse comment: Alan Harder added a comment - 2010-03-13 08:39

Alan Harder added a comment - 2010-03-13 08:39

do your jobs point to a custom workspace or let Hudson do the original checkout?

Expand comment: Alan Harder added a comment - 2010-03-13 08:39

Alan Harder added a comment - 2010-03-13 08:39 do your jobs point to a custom workspace or let Hudson do the original checkout?

Collapse comment: Anne Stellingwerf added a comment - 2010-03-13 08:52

Anne Stellingwerf added a comment - 2010-03-13 08:52

I use a free-style software project and use the default svnkit in hudson to checkout/update/revert.

Expand comment: Anne Stellingwerf added a comment - 2010-03-13 08:52

Anne Stellingwerf added a comment - 2010-03-13 08:52 I use a free-style software project and use the default svnkit in hudson to checkout/update/revert.

Collapse comment: Andrea Barbieri added a comment - 2010-03-13 08:54, Edited by Andrea Barbieri - 2010-03-13 08:55

Andrea Barbieri added a comment - 2010-03-13 08:54 - edited

in my case we always use the default workspace and the subversion plugin (with svnkit). Projects are either free-style or maven2.

I think this is the reason for the trigger (in some of my cases)

after a successful build during the normal SCM poll checks I do experience from time to time a socket connection timeout (SVN repo server) and this triggers somehow the workspace to be deleted (SVN use update option unchecked). Once the workspace is gone another build will be triggered at the next successful SCM poll attempt (even though it claims no SCM changes).

Expand comment: Andrea Barbieri added a comment - 2010-03-13 08:54, Edited by Andrea Barbieri - 2010-03-13 08:55

Andrea Barbieri added a comment - 2010-03-13 08:54 - edited in my case we always use the default workspace and the subversion plugin (with svnkit). Projects are either free-style or maven2. I think this is the reason for the trigger (in some of my cases) after a successful build during the normal SCM poll checks I do experience from time to time a socket connection timeout (SVN repo server) and this triggers somehow the workspace to be deleted (SVN use update option unchecked). Once the workspace is gone another build will be triggered at the next successful SCM poll attempt (even though it claims no SCM changes).

Collapse comment: Andrea Barbieri added a comment - 2010-07-03 03:26

Andrea Barbieri added a comment - 2010-07-03 03:26

fixed with Subversion plugin Version 1.17 (Apr 21, 2010)

Expand comment: Andrea Barbieri added a comment - 2010-07-03 03:26

Andrea Barbieri added a comment - 2010-07-03 03:26 fixed with Subversion plugin Version 1.17 (Apr 21, 2010)