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

TextFinder- & Claim-Plugin are not working properly together

    XMLWordPrintable

Details

    Description

      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.

      Attachments

        Issue Links

          Activity

            moritzp82 Moritz P added a comment -

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

            moritzp82 Moritz P added a comment - Hi ki82 , do you have any idea on how to fix this one and how long it might take?
            greybird 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

            greybird 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 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 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.

            People

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

              Dates

                Created:
                Updated:
                Resolved: