Maven Metadata Plugin

Project Status

This project is looking for maintainers. Our current work and responsibilities don't include this plugin and we not able to properly maintain it anymore. If you want to adopt this plugin see https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/

About

This plugin adds a new build parameter List maven artifact versions. If you select this type and enter a repositoryURL, groupId and artifactId the plugin will check for that artifact at the given repository and let whoever started the build select a version of the artifact to bind as a build parameter.

There are also several options to provide default values which will also be evaluated at run-time:

FIRST - will evaluate to the first item in the drop-down that would have been presented had the build been executed manually
LAST - will evaluate to the last item in the drop-down that would have been presented had the build been executed manually.
RELEASE - will evaluate to the version marked as release in the maven-metadata.xml for the configured artifact. The versionFilter even if defined is ignored for this default value.
LATEST - will evaluate to the version marked as latest in the maven-metadata.xml for the configured artifact. The versionFilter even if defined is ignored for this default value.

This plugin does not download anything but rather sets build environment variables describing the artifact and where it can be downloaded from.

If all you need to do is download an artifact from a repository and use it during your build you can consider using the Repository Connector Plugin plugin instead.

Development

Requirements

Built and tested against Jenkins 2.32.1.

Development workspace

When starting the development Jenkins using mvn hpi:run and the work directory containing the JENKINS_HOME doesn't already exist, the workspace will be created with some pre-configured test jobs for the plugin. The re-creation of the development workspace can be forced by deleting the work directory before running mvn hpi:run - of course, all manual changes, as well as build histories will be lost then.

If You're developing behind a proxy and/or a Maven Repository Manager, it may be useful to change the repoBaseUrl to the base URL of Your organisations repository manager. This can easily be achieved by setting the system property dev.repoBaseUrl when starting the development Jenkins for the first time (after the work directory was deleted). You may just set the system property in Your MAVEN_OPTS...

Authors & Contributors

Author:

Georgi "Gesh" Markov @markov

Further maintainer(s):

Marc Rohlfs @marcrohlfs

Contributors:

Benjamin Bonnet @bonnetb
David Portabella @dportabella
Dominik Bartholdi @imod
Mathieu Pousse @mathieu-pousse
Mads Mohr Christensen @hrmohr
Nandor Galambosi @dromie
Robert Kleinschmager @barclay-reg

References

Copyright & License

Licensed under the MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

basil/maven-metadata-plugin