Task Scanner Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID tasks Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
4.39
Feb 10, 2014
1.424
dashboard-view (version:2.2, optional)
token-macro (version:1.5.1, optional)
maven-plugin (version:1.424, optional)
analysis-core (version:1.55)
Source Code
Issue Tracking
Maintainer(s)
GitHub
Open Issues
Ulli Hafner (id: drulli)
Usage Installations 2013-Apr 3988
2013-May 4005
2013-Jun 4054
2013-Jul 4117
2013-Aug 3943
2013-Sep 4067
2013-Oct 4153
2013-Nov 4090
2013-Dec 3942
2014-Jan 4095
2014-Feb 4225
2014-Mar 4306


This plugin scans the workspace files for open tasks and generates a trend report.

Installation Requirements
This plug-in requires the utility plug-in "analysis-core" (called "Static Analysis Utilities" in the update manager). Please ensure that the latest version of this plug-in is also installed.

It's about 5 years now since my first Jenkins commit. I hope that you all enjoy using my static code analysis plug-ins and that these plug-ins are very helpful for your projects! There is now an easy way to support the development of these open source plug-ins I just released my Android game Inca Trails. So feel free to support my work for Jenkins by buying this game in Google Play. Of course, the game is worth its price anyway

Description


 
This plug-in is supported by the Static Analysis Collector plug-in that collects different analysis results and shows the results in aggregated trend graphs. Additionally, health reporting and build stability is also based on the aggregated results.

The tasks scanner plug-in scans the workspace files for open tasks like TODO, FIXME, or @deprecated. It is inspired by the maven taglist plug-in. This plug-in is part of the suite of static code analysis plug-ins that are documented on a separate WIKI page.

  • You can specify the files to scan after a build
  • Three configurable priority levels are supported (e.g. HIGH=FIXME, NORMAL=TODO, LOW=@deprecated)
  • Several trend reports showing the number of tasks per build
  • Overview of the found tasks per module or package
    • Parsing of Maven pom.xml or Ant build.xml configuration files to obtain the module or project name
    • Parsing of Java or C# files to obtain the package or name space name
  • Detail reports of the found tasks filtered by severity
  • Colored HTML display of the corresponding source files and with direct links to the tasks
  • Highlighting of the line that contains a task (with a tool tip showing the priority)
  • Failure threshold to mark a build as unstable
  • Configurable project health support
  • Works with the freestyle and native m2 build option
  • Remote API to export the build quality and found open tasks
  • Several tokens to simplify post processing of the results
  • Localization available for: DE, JA (Please help to localize task scanner for your locale!)

The current release is available in the download section. This plug-in is developed and maintained by Ullrich Hafner. Please use the mailing lists or issue tracker to ask questions, create feature request or bug reports, since I don't read the comment section on this page regularly.

Configuration

Configuring the plug-in should be self-explanatory: You simply need to activate the task scanner plug-in as shown below. Add the tag keywords you would like to use and save the configuration. Then the next build will report the number of open tasks and show the trend.


Changelog

You can support the development of this open source plug-ins by buying my Android game Inca Trails in Google Play!

Release 4.38

  • Added a view column that shows the number of open tasks in a job

Release 4.37

  • Make dependency to ant-plugin optional

Release 4.36

  • Show more details in the fixed warnings view (issue #15959)
  • Aggregate the maven parent module results in failed builds when the failure is caused by a threshold being hit (issue #15324, issue #12342)
  • Optimized http requests for static resources in the analysis plugins (issue #16571)
  • Fixed missing build overview in maven jobs (issue #16518)
  • Always use Xerces when parsing XML files (issue #15613)
  • Read pom.xml to obtain path of output files in maven jobs (issue #16250)
  • Show error message as file content if the source files could not be transferred to the master (issue #16222)

Release 4.35

  • Added option to consider only stable builds when calculating new warnings (Thanks to David Pärsson for the patch, issue #15037)
  • Fixed NPE when comparing warnings (issue #15414, issue #15250)

Release 4.34

Release 4.33

Release 4.32

  • Reduce memory footprint of plug-in (thanks to Kohsuke for the patches)
  • Upgrade to YUI 2.9 (support for new bread crumbs and context menus: issue #13532, thanks to OHTAKE Tomohiro for the patch)

Release 4.31

  • Show all values of difference graph

Release 4.30

  • Added hyperlinks to build summary if threshold is exceeded (issue #12424)

Release 4.29

  • Added option to filter projects with zero warnings in the warnings dashboard portlet (issue #12984)
  • Center the affected source line in source view (issue #13491)
  • Fixed incompatibility of detail tabs with new bread crumb view (issue #13532)

Release 4.28

  • Added a new portlet that shows the warning totals as a line graph
  • Added help for pattern fields (issue #13397).

Release 4.27

  • Show build result threshold evaluation information in build summary (issue #12424)
  • Support for column ranges in warnings (issue #12822)
  • Fixed plug-in configuration if used in conjunction with flexible-publisher plug-in (issue #12182, issue #8185)
  • Added support for non-alphanumeric characters when scanning for warning tags (issue #12782)

Release 4.26

  • Fixed initialization problem when configuring the plug-in for maven jobs. (issue #12075)

Release 4.25

  • Fixed NPE while configuring a graph with no builds yet (issue #12045)
  • Group warnings by relative path if the associated language has no package or namespace concept (issue #11846)
  • Allow skipping of calculating "new" issues (issue #11761)
  • Fixed display of 'Use delta for new warnings' option (issue #11758)
  • Ignore 'new warnings' threshold in the first build (issue #11718)
  • Don't count warnings twice (in sub-modules of maven jobs) (issue #11571)

Release 4.24

  • Don't scan module sub-folders of maven projects (packaging pom) for open tasks (issue #11571)

Release 4.23

  • Fixed empty tasks report in maven projects (report)

Release 4.22

  • Fixed enlarge link for trend graphs (issue #11324)
  • Fixed visibility of 'enable trend graph' link

Release 4.21

  • Ignore failed builds when evaluating the build history in trend graphs and new warnings calculation (issue #10682)
  • Added OSGi bundle detection when grouping warnings by module (issue #10681)
  • Use the path as a replacement for the package grouping for all warnings that are not from Java or C# files (issue 2)
  • Cancel parsing if the build has been aborted by the current user (issue #10627, issue #9158)
  • Ignore not accessible files during parsing (issue #10626)

Release 4.20

  • Added new tokens for token macro plug-in (issue #10027): now tokens TASKS_NEW, TASKS_FIXED, TASKS_COUNT and TASKS_RESULT are available.

Release 4.19

Release 4.18

  • Fixed display of trend graphs for maven jobs (report)

Release 4.17

  • Fixed health reporting and build failure/unstable thresholds for maven project type (issue #4912, issue #3514)
  • Fixed broken detail views when using a reverse proxy (issue #3410, thanks to Benjamin Cabé for the fix)
  • Show the reference build that is used to compute new and fixed warnings (when build thresholds are set)
  • Improved logging statements when build is executed on a slave

Release 4.16

  • Added configuration option to enable automatic project and module name detection by reading all Ant project.xml and Maven pom.xml files (issue #8915, issue #9090)
  • Added preliminary support for the Token Macro Plugin: TASKS_COUNT expands to the number of open tasks and TASKS_RESULT expands to the plug-in build result (stable, unstable, failed)

Release 4.15

  • Fixed missing dependency to Hudson/Jenkins 1.395 (issue #8509)

Release 4.14

  • Jenkins update to links and documentation
  • Show progress text while dashboard portlet graphs are created

Release 4.13

  • Added support for multi-configuration projects (issue #6772)
  • Fixed broken links in details view (issue #8167)

Release 4.12

  • Fixed sorting of date labels of dashboard trend graphs (issue #8476)
  • Fixed evaluation of builds that will be considered in the dashboard trend graph (issue #8283)

Release 4.11

  • Added build status thresholds for each warning priority (issue #3561)

Release 4.10

  • Fixed computation of module names for maven projects (issue #6768)
  • Don't report an error message if a maven module does not contain a report file (issue #6895)
  • Fixed ant links (issue #6862)

Release 4.9

  • Fixed naming of maven modules (issue #6513)
  • Group files by path if there is no package or namespace found (issue #6698)

Release 4.8

Release 4.7

  • Fixed broken links to project page and overview image (issue #6417)

Release 4.6

  • Added trend graph portlets for the dashboard view
  • Added option to start the plug-in even for failed builds (issue #6117)
  • Added 'enlarge' link for trend graphs that shows a detail page with the graph
  • Fixed ordering of warnings in detail views (issue #6132)
  • Fixed warning distribution graph in files detail view (issue #6139)

Release 4.4

Release 4.3

  • New warnings computation is now based on the current build and the reference build (i.e., the last successful build, see issue #5147)
  • Visualized plug-in build status (based on the healthiness thresholds)
  • Added high scores for successful builds
  • Don't show project action if there are no warnings (issue #5473)
  • Don't show trend graph configuration on job creation (issue #5294)
  • Improved remote API, now the warning keys are also exposed (issue #5195)

Release 4.2

  • Added support for the new plug-in [Static Analysis Collector plug-in] to provide combined trend graphs and health reporting (issue #3320)
  • Improved remote API, now the warnings are also exposed (issue #5195)

Release 4.1

  • Include test sources and resources when scanning the workspace of maven projects (issue #5136)
  • Fixed permissions for viewing the source code, now the WORKSPACE permission is used
  • Fixed trend report link if there are no results available yet (issue #5156)
  • Fixed preview of trend reports
  • Added dependency to Hudson 1.337 due to a class loader bug in previous versions (issue #4993)

Release 4.0

  • Extracted common code of the static code analysis plug-ins into a new utility plug-in "analysis-core"
  • Several bug fixes and small improvements

Release 1.x - 3.x ChangeLog

Labels

Edit
plugin-report plugin-report Delete
plugin-maven plugin-maven Delete
supports-dashboard-view supports-dashboard-view Delete
token-producer token-producer Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Add Comment