Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41652

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

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            andreask Andreas Kühle created issue -
            andreask Andreas Kühle made changes -
            Field Original Value New Value
            Priority Major [ 3 ] Critical [ 2 ]
            andreask Andreas Kühle made changes -
            Environment Jenkins 2.19.4 installed on Win 2008R2 using Tomcat 8
            Subversion-Plugin 2.7.1
            Subversion-Server 1.8.9
            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
            andreask Andreas Kühle made changes -
            Description 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.
            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.
            andreask Andreas Kühle made changes -
            Summary Build only triggered by svn-post-commit-hook if previous build was stable Build only triggered by post-commit-hook if previous build was stable
            andreask Andreas Kühle made changes -
            Labels commit-hook jenkins subversion commit-hook git git-plugin jenkins subversion subversion-plugin
            andreask Andreas Kühle made changes -
            Component/s git-plugin [ 15543 ]
            markewaite Mark Waite made changes -
            Component/s git-plugin [ 15543 ]
            andreask Andreas Kühle made changes -
            Description 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.
            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.
            jglick Jesse Glick made changes -
            Link This issue duplicates JENKINS-40255 [ JENKINS-40255 ]
            jglick Jesse Glick made changes -
            Resolution Duplicate [ 3 ]
            Status Open [ 1 ] Resolved [ 5 ]

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              andreask Andreas Kühle
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: