Lucene-Search adds support to search for build data using the Jenkins search box (aka quick navigation). The plugin stores the data after each build in a search database.


Install it as a normal plugin and all new builds will be searchable.

Before old builds can be searched, a "Rebuild database" must be performed via the "Manage Jenkins" >>> "Lucene Search Manager". This step should never have to be done again, but may take a long time if you have many jobs and builds.

Upgrade to Lucene-Search 4.x

Version 4.0 changed Lucene search engine from version 4 to version 5 so you should recreate the Lucene database after upgrade.

Supported keywords

console: Console output 
projectdisplayname: The project display name
projectname: The project name
buildnumber: Project build number*
id: The unique ID generated by Jenkins*
duration: Build duration in ms*
starttime: Start time in ms*
builton: Node name for where the build was run
startcause: Who or what started the build
color: Icon color for the build*'
result: Build result, case sensitive. Example SUCCESS, FAILURE

* Not included in the default search

For more information on how to use search usnig Lucene read 



The easiest way to get Solr up and running is by downloading the lastest stable version (5.3.1 at the time of writing), unpack and do the following:

cd solr-5.3.1/example/example-schemaless
java -jar ../start.jar

Lucene-Search will set up the fields before it needs them. Adding fields via extension points will require restarting jenkins or reconfiguring the plugin (known bug).

Extension point

If you are a developer and want to add your own data to the database you can implement the extension point "FreeTextSearchExtension". This will allow the Lucene plugin to add your data to the database so it can be searched. It is NOT an all or nothing deal, it's easy to support Lucene-Search without requiring it.

Maven dependency

    <optional>true</optional> <!-- Only support, not require, lucene-search -->



is to only add support for Lucene-Search. This is for when you have a plugin that can use Lucene-Search, but doesn't require it for the plugin to work. If Lucene-Search is in the Jenkins instance at runtime, the Lucene-Search plugin will use the extension points defined by the plugin. If not, the ExtensionPoint will not cause any problems.


import org.jenkinsci.plugins.lucene.search.FreeTextSearchExtension;

public class FitFreeTextSearchExtension extends FreeTextSearchExtension {

    public String getKeyword() {
        return "fitsummary";

    public String getTextResult(AbstractBuild<?, ?> build) {
        StringBuilder builder = new StringBuilder();

        for (FitSummaryAction action : build.getActions(FitSummaryAction.class)) {
            builder.append(action.getSummary() + "\n");

        return builder.toString();


    public boolean isPersist() {
        return true;


Coming changes (completed/prioritized)


  1. Improve console hightlightings. "(exit code: 1)" hightlights the word code and the number 1. Would be better if we only hightlight the full match. -Command completed with code 0
  2. Paginating results.
  3. Find a solution for  the bugs JENKINS-30325 and 30665 where we can not use Lucene without "XX:-UseSplitVerifier" after Jenkins 1.602


JDK Version

The Lucene lib used by this plugin requires that we run Jenkins with Java 7 or later. However due to a bug in Jenkins byte code this plugin will not work if you use Java 8 with a Jenkins version later then 1.601. If you are running on a newer version you will need to run with Java 7 and add the java argument XX:-UseSplitVerifier when starting Jenkins or you will be unable to use the search function.

For more information see Jenkins defect 30665 



How to search

Just a type a string in the search box to search. If you do not include a suffix the search plugin will search in all keywords bellow not marked with a *. If you want to search for a string in a specific field just add the write <KEYWORDS>:<VALUE>.

IndexWriter is locked

This problem is seen for several reasons
* The lucene folder on the Jenkins server has invalid user permisions, change the read/write permisions and reconfigure Lucene/restart the Jenkins server
* Out of permgen memory on Jenkins
* The solr server has crashed, often as you don't have enough memory on the server.


Version 4.2 (release Dec 21, 2015) 

Version 4.1 (release Dec 19, 2015) 

Version 4.0 (release Dec 18, 2015) 

Version 3.0 (release Oct 15, 2015)

Version 2.1 (release Sep 8, 2015)

Version 1.15 (released Apr 15, 2015)

Version 1.14 (released Apr 15, 2015)

Version 1.13 (released Apr 7, 2015)

Version 1.12 (released Apr 1, 2015)

Version 1.11 (released Mar 29, 2015)

Version 1.10 (released Mar 26, 2015)

Version 1.9 (released Mar 18, 2015)

Version 1.8 (released Mar 10, 2015)

Version 1.6 (released Mar 5, 2015)

Version 1.2 (released Sep 3, 2014)

Version 1.1 (released Aug 31, 2014)

Version 1.0 (released Aug 31, 2014)