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/
This plugin adds a new build parameter List maven artifact versions. If you select this type and enter a
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
releasein 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
latestin 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.
For example: In your configuration you have created a parameter named
MY_JAR and have configured all values correctly. Then the following parameters will be set for the build step:
MY_JAR_VERSION- the version you selected in the dropdown or that was selected as part of an automated build
MY_JAR_ARTIFACT_URL- the full URL to the actual artifact selected. You can use something like
wgetto download that artifact and do something with it.
MY_JAR_GROUP_ID- echoes back your configuration
MY_JAR_ARTIFACT_ID- echoes back your configuration
MY_JAR_CLASSIFIER- echoes back your configuration
MY_JAR_PACKAGING- echoes back your configuration
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.
Built and tested against Jenkins 2.32.1.
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
- Georgi "Gesh" Markov @markov
- Marc Rohlfs @marcrohlfs
- Benjamin Bonnet @bonnetb
- David Portabella @dportabella
- Dominik Bartholdi @imod
- Mathieu Pousse @mathieu-pousse
- Mads Mohr Christensen @hrmohr
- Nandor Galambosi @dromie
- Robert Kleinschmager @barclay-reg
Copyright:: 2012-2014, Georgi "Gesh" Markov
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.