• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • subversion-plugin
    • None
    • Jenkins 2.346.2
      subversion-plugin 2.16.0
      java_version 1.8.0_181

      I have many jobs in jenkins in which I use plugin "Subversion Plug-in". I use settings as screen1 and screen2. In svn server installed post-commit hook like in documentation https://plugins.jenkins.io/subversion/.
      When I make commit in my repo I expect this commit trigger my job but this is not happen. I see that my jenkins recive hook, but the task does not start.
      For example, I make commit to repo "pNRPT/Projects/DEVOPS/*" and see log in Jenkins:

      авг 10, 2022 12:45:12 AM FINER hudson.scm.SubversionRepositoryStatus
      Reading line: U   pNRPT/Projects/DEVOPS/test.txt
      авг 10, 2022 12:45:12 AM FINE hudson.scm.SubversionRepositoryStatus
      Change reported to Subversion repository f4a00ee3-6796-0442-a6fd-adcae048c563 on [pNRPT/Projects/DEVOPS/test.txt]
      авг 10, 2022 12:45:12 AM FINE hudson.scm.SubversionRepositoryStatus
      Starting subversion locations checks for all jobs
      авг 10, 2022 12:45:12 AM FINE hudson.scm.SubversionRepositoryStatus
      Ended subversion locations checks for all jobs
      авг 10, 2022 12:45:12 AM WARNING hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl onNotify
      No subversion jobs found
      авг 10, 2022 12:45:12 AM WARNING hudson.scm.SubversionRepositoryStatus doNotifyCommit
      No interest in change to repository UUID f4a00ee3-6796-0442-a6fd-adcae048c563 found

      Why Jenkins cann't find changes? SVN uuid is correct. If I manually start the job or set the schedule in pool SCM, then the job will be done.

      I tried to install and configure another svn server and got the same result and I  think that problem in Jenkins or Jenkins plugin.

          [JENKINS-69300] Post-commit hooks don't start jobs

          Claudio Weiler added a comment - - edited

          Maybe related to JENKINS-69295?

          Claudio Weiler added a comment - - edited Maybe related to JENKINS-69295 ?

          claudioweiler I do not know, maybe it is related. In our builds, in order to always have a fresh copy, we use workspaceUpdater: [$class: 'CheckoutUpdater']]. The truth is that in our case, the hook also worked at first, and then it's not even clear when and why it stopped.

          Sergey Beketov added a comment - claudioweiler I do not know, maybe it is related. In our builds, in order to always have a fresh copy, we use workspaceUpdater: [$class: 'CheckoutUpdater'] ]. The truth is that in our case, the hook also worked at first, and then it's not even clear when and why it stopped.

          It was a Jenkins bug related to user rights in the matrix of the roles. A user logged into jenkins is case sensitive. In the role matrix, my user was entered incorrectly (only in small letters), but it could be noticed in the first 3 seconds when the role matrix page is loaded.

           

          Sergey Beketov added a comment - It was a Jenkins bug related to user rights in the matrix of the roles. A user logged into jenkins is case sensitive. In the role matrix, my user was entered incorrectly (only in small letters), but it could be noticed in the first 3 seconds when the role matrix page is loaded.  

            Unassigned Unassigned
            beketovsv Sergey Beketov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: