• Type: Bug
• Resolution: Duplicate
• Priority: Critical
• Component/s: core, subversion-plugin
• Labels:

  • commit-hook
  • git
  • git-plugin
  • jenkins
  • subversion
  • subversion-plugin
• Environment:

  Jenkins 2.19.4,
  Jenkins 2.32.2 both installed on Win 2008R2 using Tomcat 8
  Subversion-Plugin 2.7.1
  Subversion-Server 1.8.9
  Git-Plugin 3.0.0
  Git 1.8.1.2

[JENKINS-41652] Build only triggered by post-commit-hook if previous build was stable

Andreas Kühle created issue - 2017-02-02 10:32

Collapse comment: Andreas Schrell added a comment - 2017-02-02 17:26

Andreas Schrell added a comment - 2017-02-02 17:26

We are using the subversion plugin in a pipeline builds. We also see empty changelogs from several builds:

• aborted by user
• failed
• when pipeline is left after an unstable step with FlowInterruptedException
  but it is inconsistent. I do not find the rules behind it. Even just after the checkout stage some builds have an empty changes list in currentBuild.

Expand comment: Andreas Schrell added a comment - 2017-02-02 17:26

Andreas Schrell added a comment - 2017-02-02 17:26 We are using the subversion plugin in a pipeline builds. We also see empty changelogs from several builds: aborted by user failed when pipeline is left after an unstable step with FlowInterruptedException but it is inconsistent. I do not find the rules behind it. Even just after the checkout stage some builds have an empty changes list in currentBuild.

Andreas Kühle made changes - 2017-02-13 12:40

Priority

Original: Major [ 3 ]

New: Critical [ 2 ]

Andreas Kühle made changes - 2017-02-13 12:47

Environment

Original: Jenkins 2.19.4 installed on Win 2008R2 using Tomcat 8 Subversion-Plugin 2.7.1 Subversion-Server 1.8.9

New: Jenkins 2.19.4, Jenkins 2.32.2 both installed on Win 2008R2 using Tomcat 8 Subversion-Plugin 2.7.1 Subversion-Server 1.8.9 Git-Plugin 3.0.0 Git 1.8.1.2

Andreas Kühle made changes - 2017-02-13 12:48

Description

Original: It seems that builds are only triggered by svn-post-commit-hook if the previous build was stable. Starting a commit-hook after a stable build will work as expected and result in: _Feb 02, 2017 9:19:02 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify Received post-commit hook from <uuid> for revision <rev> on paths <path> Feb 02, 2017 9:19:02 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify No subversion consumers for UUID <uuid> Feb 02, 2017 9:19:02 AM INFO hudson.triggers.SCMTrigger$Runner run SCM changes detected in <job>. Triggering #17 Feb 02, 2017 9:19:40 AM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finish <job> #17 completed: SUCCESS_ As soon as the previous build isn't stable or doesn't exist the commit-hook seems to be noticed but there aren't any connected projects found: _Feb 02, 2017 9:25:28 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify Received post-commit hook from <uuid> for revision <rev> on paths <path> Feb 02, 2017 9:25:28 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify No subversion consumers for UUID <uuid> Feb 02, 2017 9:27:11 AM WARNING hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl onNotify No subversion jobs using repository: <uuid> _ Additionally the changelog of failed builds is empty. There's also no information about the used scm-revision.

New: It seems that builds are only triggered by post-commit-hook if the previous build was stable. Starting a commit-hook after a stable build will work as expected and result in: _Feb 02, 2017 9:19:02 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify Received post-commit hook from <uuid> for revision <rev> on paths <path> Feb 02, 2017 9:19:02 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify No subversion consumers for UUID <uuid> Feb 02, 2017 9:19:02 AM INFO hudson.triggers.SCMTrigger$Runner run SCM changes detected in <job>. Triggering #17 Feb 02, 2017 9:19:40 AM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finish <job> #17 completed: SUCCESS_ As soon as the previous build isn't stable or doesn't exist the commit-hook seems to be noticed but there aren't any connected projects found: _Feb 02, 2017 9:25:28 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify Received post-commit hook from <uuid> for revision <rev> on paths <path> Feb 02, 2017 9:25:28 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify No subversion consumers for UUID <uuid> Feb 02, 2017 9:27:11 AM WARNING hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl onNotify No subversion jobs using repository: <uuid> _ Additionally the changelog of failed builds is empty. There's also no information about the used scm-revision.

Andreas Kühle made changes - 2017-02-13 12:48

Summary

Original: Build only triggered by svn-post-commit-hook if previous build was stable

New: Build only triggered by post-commit-hook if previous build was stable

Andreas Kühle made changes - 2017-02-13 12:49

Labels

Original: commit-hook jenkins subversion

New: commit-hook git git-plugin jenkins subversion subversion-plugin

Andreas Kühle made changes - 2017-02-13 12:49

Component/s

New: git-plugin [ 15543 ]

Mark Waite made changes - 2017-02-14 17:55

Component/s

Original: git-plugin [ 15543 ]

Andreas Kühle made changes - 2017-02-17 14:18

Description

Original: It seems that builds are only triggered by post-commit-hook if the previous build was stable. Starting a commit-hook after a stable build will work as expected and result in: _Feb 02, 2017 9:19:02 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify Received post-commit hook from <uuid> for revision <rev> on paths <path> Feb 02, 2017 9:19:02 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify No subversion consumers for UUID <uuid> Feb 02, 2017 9:19:02 AM INFO hudson.triggers.SCMTrigger$Runner run SCM changes detected in <job>. Triggering #17 Feb 02, 2017 9:19:40 AM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finish <job> #17 completed: SUCCESS_ As soon as the previous build isn't stable or doesn't exist the commit-hook seems to be noticed but there aren't any connected projects found: _Feb 02, 2017 9:25:28 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify Received post-commit hook from <uuid> for revision <rev> on paths <path> Feb 02, 2017 9:25:28 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify No subversion consumers for UUID <uuid> Feb 02, 2017 9:27:11 AM WARNING hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl onNotify No subversion jobs using repository: <uuid> _ Additionally the changelog of failed builds is empty. There's also no information about the used scm-revision.

New: It seems that builds are only triggered by post-commit-hook if the previous build was stable. Starting a commit-hook after a stable build will work as expected and result in: _Feb 02, 2017 9:19:02 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify Received post-commit hook from <uuid> for revision <rev> on paths <path> Feb 02, 2017 9:19:02 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify No subversion consumers for UUID <uuid> Feb 02, 2017 9:19:02 AM INFO hudson.triggers.SCMTrigger$Runner run SCM changes detected in <job>. Triggering #17 Feb 02, 2017 9:19:40 AM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finish <job> #17 completed: SUCCESS_ As soon as the previous build isn't stable or doesn't exist the commit-hook seems to be noticed but there aren't any connected projects found: _Feb 02, 2017 9:25:28 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify Received post-commit hook from <uuid> for revision <rev> on paths <path> Feb 02, 2017 9:25:28 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify No subversion consumers for UUID <uuid> Feb 02, 2017 9:27:11 AM WARNING hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl onNotify No subversion jobs using repository: <uuid> _ Additionally the changelog of failed builds is empty. There's also no information about the used scm-revision. Furthermore it is not possible to trigger multiple projects via the same commit-hook.

Load more newer events