The POM file

The last remaining file, pom.xml, is the Maven settings file that we have looked at before. This one is particular to the plugin we are using here and contains the group, artifact, and version information that will be used to build, run, and package the project, which we will do now.

Right-clicking on the pom.xml file and selecting Run as and then Maven Build… allows you to specify the hpi:run goal again, which should start up a new local instance of Jenkins with this plugin compiled and deployed to this new instance, along with all of the resources and localization settings the plugin contains.

When the instance starts up, we can connect via a browser and see the various settings and code that we have reviewed in theory being used in practice.

We can check and see that the plugin is listed as installed, along with the message text, which is picked up from index.jelly:

When we create a new Freestyle job and take a look at the available Build steps that we could add, this plugin...