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

TaskScanner Plugin creates too many links "OpenTasks"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • tasks-plugin
    • Jenkins 2.65
      Task Scanner Plugin 4.51
      Pipeline Job

      Task Scanner generates new links "Open Tasks" on the left (cf screenshot in attachement)

      All of the links open the same URL .../MY_JOB/BUILD_NUMBER/tasksResult/ 

      Note : I use 4 build steps "withMaven" that automatically generates reports (junit, findbugs and Tasks). They are used in different stages of my pipeline.

      one of them in example (nothing special)

      withMaven(jdk: "${jdkVersion}", maven: "${mavenVersion}", mavenLocalRepo: '${workspace}/.repository', mavenOpts: '', mavenSettingsFilePath: '') {
     timestamps {
         sh "mvn -s settings.xml verify site -fn -DskipTests" 
     }
 }

      Expected result : Only one link should be displayed in the left Menu of the job

        1. taskScannerPlugin.JPG
          taskScannerPlugin.JPG
          41 kB

          [JENKINS-47200] TaskScanner Plugin creates too many links "OpenTasks"

          Ulli Hafner added a comment -

          Please comment your requirements in the corresponding wiki page.

          Ulli Hafner added a comment - Please comment your requirements in the corresponding wiki page .

          Ulli Hafner added a comment -

          Is this automatic invocation of the analysis plugins using the withMaven block required? Or would it be just fine if you call these steps manually?

          Ulli Hafner added a comment - Is this automatic invocation of the analysis plugins using the withMaven block required? Or would it be just fine if you call these steps manually?

          Thomas COAN added a comment -

          Yes, I can call the steps manually. 

          does it solve the problem ? => 1 call of taskscanner generates only 1 link "Open Task" 

           

          in order to run code analysis, will I need to do something like that (example from your wiki) ?
          sh "${mvnHome}/bin/mvn -batch-mode -V -U -e checkstyle:checkstyle pmd:pmd findbugs:findbugs"
                  def checkstyle = scanForIssues tool: [$}}{{class}}{{: }}{{'CheckStyle'}}{{], pattern: '**/checkstyle-result.xml'
                  publishIssues issues:[checkstyle], useStableBuildAsReference: true
           

          Thomas COAN added a comment - Yes, I can call the steps manually.  does it solve the problem ? => 1 call of taskscanner generates only 1 link "Open Task"    in order to run code analysis, will I need to do something like that (example from your wiki) ? sh  "${mvnHome}/bin/mvn -batch-mode -V -U -e checkstyle:checkstyle pmd:pmd findbugs:findbugs"           def   checkstyle = scanForIssues tool: [$}}{{class}}{{: }}{{'CheckStyle'}}{{] , pattern:  '**/checkstyle-result.xml'          publishIssues issues: [checkstyle] , useStableBuildAsReference: true  

          Ulli Hafner added a comment - - edited

          (Hint: You can wrap sh Scripts using the noformat tag in Confluence.)

          The new approach will be:

          1. Collect the open tasks
          2. Publish the open tasks

          In step 2 you can combine the results of 'n' results that have been obtained in step 1

          Ulli Hafner added a comment - - edited (Hint: You can wrap sh Scripts using the noformat tag in Confluence.) The new approach will be: Collect the open tasks Publish the open tasks In step 2 you can combine the results of 'n' results that have been obtained in step 1

          Thomas COAN added a comment -

          Ok seems good to me, thanks Ulli.

          I wait for the new version

          Thomas COAN added a comment - Ok seems good to me, thanks Ulli. I wait for the new version

            drulli Ulli Hafner
            tcoan Thomas COAN
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: