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

TextFinder- & Claim-Plugin are not working properly together

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • claim-plugin
    • None

      We're using the text-finder plugin to change some jobs' status to unstable and the claim plugin to allow all devs to claim the jobs.

      publishers {
  allowBrokenBuildClaiming()
  textFinder("echo 'TESTS FAILED'", '', true, false, true)
  archiveJunit("report/tests/*.xml")
}

      The resulting job configuration looks like shown on the attached screenshot.
      The problem is, that you won't be able to claim the job if it was set to unstable by the textFinder-Plugin. From what I read so far, the dependency in between publisher plugins should be managed internally but to me it looks like the dependency between the two plugins is not managed correctly. If moving the allow claiming part behind the textFinder within the ui configuration, it works.

        1. Screen Shot 2016-08-10 at 09.56.41.png
          Screen Shot 2016-08-10 at 09.56.41.png
          103 kB

          [JENKINS-37299] TextFinder- & Claim-Plugin are not working properly together

          Moritz P added a comment -

          Hi ki82, do you have any idea on how to fix this one and how long it might take?

          Moritz P added a comment - Hi ki82 , do you have any idea on how to fix this one and how long it might take?

          Arnaud TAMAILLON added a comment - - edited

          Issue is within Jenkins core, and likely not to be fixed.

          https://groups.google.com/forum/#!topic/jenkinsci-dev/BjsZyXx9vY8

          Arnaud TAMAILLON added a comment - - edited Issue is within Jenkins core, and likely not to be fixed. https://groups.google.com/forum/#!topic/jenkinsci-dev/BjsZyXx9vY8

          Basil Crow added a comment -

          Removing the "Text Finder" component from the list of components, since there is no code that needs to be updated there. As Arnaud mentioned, the issue is within Jenkins core.

          Basil Crow added a comment - Removing the "Text Finder" component from the list of components, since there is no code that needs to be updated there. As Arnaud mentioned, the issue is within Jenkins core.

            greybird Arnaud TAMAILLON
            moritzp82 Moritz P
            Votes:
            9 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: