Metadata search view and result.
You can also add a metadata filter to a view where you can provide a search string that will filter out the jobs matching that search.
{jenkins-plugin-info:metadata|jiraComponent=metadata-plugin} |
This plugin allows metadata to be added to projects, builds and slaves in Jenkins. |
The main idea of the metadata plugin is to make searching for jobs and builds to behave more like a database, and act as an enabler for other plugins.
Once all the information about a project is gathered in one place, plugins can be developed to use this information, as well as to provide information.
The more plugins that provide information, the more usable data you can search for.
As an example of using the information, look at the External Resource Dispatcher plugin.
We differentiate between MetadataDefinitions and MetadataValues. The idea comes from the parameter setup in Jenkins.
A MetadataValue is what's set on the configuration page of a project or slave and is also what is saved for a build.
MetadataDefinitions are used by admins for making sure that certain metadata exist on all projects.
A MetadataDefinition is set up through a special configuration page, configuring a name and default value for the definition.
Once set, the MetadataDefinition will end up in all projects on the server, prompting the user to set a value for it when the project is configured.
MetadataDefinitions are then converted to MetadataValues.
These are the metadata types currently available. More will be added, and plugin developers could add their own types.
All MetadataValues for a project will automatically get copied to each build on that project. Metadata for a project or a build can be
seen by clicking the "Metadata" link from the project or the build, respectively.
If "Expose to environment" is checked for a MetadataValue, the value will also be made available as an environment variable like this:
TreeNodeMetadataValue with name "my" with one child, a StringMetadataValue with name "string" and value "value".
This will be converted to an environment variable called MD_MY_STRING with value "value".
That is, MD (short for metadata) will be prepended, and each parent-child bond will be represented by an underscore.
These environment variables can then be used by the build.
The search functionality is accessible through the "Metadata search" link.
Currently, only searching for projects is supported, but builds and slaves will be added.
Searching is done with the syntax metadatavaluename=value && othervaluename=value2
Equals, And and Or (||) are the operators supported so far.
Metadata search view and result.
You can also add a metadata filter to a view where you can provide a search string that will filter out the jobs matching that search.
Plugin developers can add their own MetadataDefinitions and Values, by extending either AbstractMetadataDefinition/Value directly or
one of the subclasses. If possible, try to use the existing classes as much as possible when providing data from your plugin as there is
no value in lots of definitions/values that do almost the same thing but with different names.
Other than writing your own MetadataDefinitions and Values, the main way of extending the Metadata plugin is through the contributor classes.
This ExtensionPoint can be used when you want to automatically add Metadata to a project whenever the project is saved. Extend JobMetadataContributor,
add @Extension to your class, and implement the getMetaDataFor method. Return a list of MetadataValues which will then be added to the project.
This ExtensionPoint can be used when you want to automatically add Metadata to a build whenever it is finished. Extend BuildMetadataContributor,
add @Extension to your class, and implement the getMetadataFor method. Return a list of MetadataValues which will then be added to the project.
Here is a list of features we would like to see in the Metadata plugin in the future:
Initial beta release