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

When tagging a Build Policiy Violation Errors fom SVN Server are not visible

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • subversion-plugin
    • jekins running on a windows box. we use svn version 1.8 on another server

      we implemented a checkin policy in our svn server. every checkin comment must fulfill these policy. otherwise the checkin is denied, the svn server genarates an error message for the client.
      this policy works fine, the error message is shown for example in tortoise client.

      then i tried to create a svn tag branch out of the jenkins gui "tag this build", my checkin comment does not match the policy. the tag was not created, but the error message of the svn server was not visible in jekins. nor did jenkins report the failure during the creation of the svn branch in any way.
      took me some time, to figure out why the branch was not created.

          [JENKINS-27846] When tagging a Build Policiy Violation Errors fom SVN Server are not visible

          Peter Ettinger created issue -
          Christopher Orr made changes -
          Component/s New: subversion-plugin [ 15485 ]
          Component/s Original: svn [ 18924 ]
          Key Original: INFRA-259 New: JENKINS-27846
          Project Original: Infrastructure [ 10301 ] New: Jenkins [ 10172 ]
          Workflow Original: jira [ 161690 ] New: JNJira [ 162436 ]
          Peter Ettinger made changes -
          Description Original: we implemented a checkin policy in our svn server. the checkin comment must fulfill these policy. otherwise the checkin is denied, the svn server genarates an error message for the client.
          this policy works fine, the error message is shown for example in tortoise client.

          then i tried to create a svn tag branch out of the jasper gui "tag this build" my checkin comment does not match the policy. the tag was not created, but the error message of the svn server was not visible in jasper. not did jasper report the failure during the creation of the svn branch in any way.
          took me some time, to figure out why the branch was not created.
          New: we implemented a checkin policy in our svn server. every checkin comment must fulfill these policy. otherwise the checkin is denied, the svn server genarates an error message for the client.
          this policy works fine, the error message is shown for example in tortoise client.

          then i tried to create a svn tag branch out of the jenkins gui "tag this build", my checkin comment does not match the policy. the tag was not created, but the error message of the svn server was not visible in jekins. nor did jenkins report the failure during the creation of the svn branch in any way.
          took me some time, to figure out why the branch was not created.
          Environment Original: svn running on a windows box. we use svn version 1.8 on another server New: jekins running on a windows box. we use svn version 1.8 on another server
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 162436 ] New: JNJira + In-Review [ 180795 ]

            pettinger Peter Ettinger
            pettinger Peter Ettinger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: