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

Provide option to specify additional source folders

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: tasks-plugin
    • Labels:
      None
    • Environment:
      Ubuntu x64, running Hudson Standalone
    • Similar Issues:

      Description

      I have created a PHP Maven project with the Maven PHP Project, enabled the Task plugin, and set the files to scan to ***/*.php

      No exclusions, typical scan of FIXME, TODO ; @deprecated, case insensitive.

      No further configuration.

      When a build is performed, I see the following output:

      [INFO] [clean:clean] [INFO] Deleting directory /var/lib/hudson/jobs/HStore/workspace/target
      [TASKS] Skipping non-existent folder '/var/lib/hudson/jobs/HStore/workspace/src/main/java'...
      [TASKS] Skipping non-existent folder '/var/lib/hudson/jobs/HStore/workspace/src/test/java'...
      [TASKS] Skipping non-existent folder '/var/lib/hudson/jobs/HStore/workspace/src/main/resources'...
      [TASKS] Skipping non-existent folder '/var/lib/hudson/jobs/HStore/workspace/src/test/resources'...
      [TASKS] Skipping maven reporter: there is already a result available

      The last line is repeated several times during build.

      The plugin seems to assume that this is a java project, and therefore searches for the default source folders, but fails to find any, since my code is in src/main/php. No php files seem to ever be scanned, and all reports show 0 tasks even when I add TODOs and FIXMEs.

        Attachments

          Issue Links

            Activity

            Hide
            robert_l Robert Lieske added a comment - - edited

            I would prefer an option to ignore the pom and behave the same as when used in Hudson/Jenkins freestyle projects.
            (which would probably mean, to scan all folders).
            This is what the user expects when specifying */.

            {extension}.
            The user can still restrict the search when not specifying */.{extension}

            , but */java//.

            {extension}

            .

            Show
            robert_l Robert Lieske added a comment - - edited I would prefer an option to ignore the pom and behave the same as when used in Hudson/Jenkins freestyle projects. (which would probably mean, to scan all folders). This is what the user expects when specifying * / . {extension}. The user can still restrict the search when not specifying * / .{extension} , but * /java/ / . {extension} .
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Ulli Hafner
            Path:
            src/main/java/hudson/plugins/tasks/TasksPublisher.java
            src/main/java/hudson/plugins/tasks/TasksReporter.java
            src/main/resources/hudson/plugins/tasks/TasksReporter/config.properties
            src/main/resources/hudson/plugins/tasks/TasksReporter/config_de.properties
            http://jenkins-ci.org/commit/tasks-plugin/42d5a2d93a8e70ac05369a6c30b14f512739617f
            Log:
            [FIXED JENKINS-6127] Parsing of maven projects now starts in pom folder.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/tasks/TasksPublisher.java src/main/java/hudson/plugins/tasks/TasksReporter.java src/main/resources/hudson/plugins/tasks/TasksReporter/config.properties src/main/resources/hudson/plugins/tasks/TasksReporter/config_de.properties http://jenkins-ci.org/commit/tasks-plugin/42d5a2d93a8e70ac05369a6c30b14f512739617f Log: [FIXED JENKINS-6127] Parsing of maven projects now starts in pom folder.
            Hide
            robert_l Robert Lieske added a comment -

            I'm using current version of Task-Plugin (4.20). My comment as of 16/Jun still applies: When used in a Maven Build Project, the scanner only trys to scan inside /java/ directories and thus does not find any TODOs/FIXMEs in my Flex-Files (which are in /flex/).

            Show
            robert_l Robert Lieske added a comment - I'm using current version of Task-Plugin (4.20). My comment as of 16/Jun still applies: When used in a Maven Build Project, the scanner only trys to scan inside /java/ directories and thus does not find any TODOs/FIXMEs in my Flex-Files (which are in /flex/ ).
            Hide
            drulli Ulli Hafner added a comment -

            Please be patient. The change is not released yet.

            You can grap a snapshot of the plugin from Jenkins on Jenkins CI instance or from http://www.faktorzehn.org:8081/job/Jenkins%20Analysis%20Plug-ins%20%28Compile%29/

            Show
            drulli Ulli Hafner added a comment - Please be patient. The change is not released yet. You can grap a snapshot of the plugin from Jenkins on Jenkins CI instance or from http://www.faktorzehn.org:8081/job/Jenkins%20Analysis%20Plug-ins%20%28Compile%29/
            Hide
            dogfood dogfood added a comment -

            Integrated in plugins_tasks #123

            Show
            dogfood dogfood added a comment - Integrated in plugins_tasks #123

              People

              • Assignee:
                drulli Ulli Hafner
                Reporter:
                jsotuyod Juan Sotuyo
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: