https://stackoverflow.com/questions/15010016
italiano
english
français
española
中国
日本の
العربية
Deutsch
한국어
Português
RussianSet up a separate Jenkins "task" that uses Maven to deploy.
Note: You don't need to know too much about Maven to make this work. You'll have to install it. You'll have to configure it as described on the page below and you'll need to call it from a command line using that information. (If you want to learn more, you can use the alternate suggesion.)
Set up the settings.xml using information from this page:
http://archiva.apache.org/docs/1.4-M2/userguide/deploy.html
That same page shows how to do it running Maven from a command line. To use this, you will create a Jenkins task that runs a shell script and deploys directly from where ever the build task creates it. Then you either run the deploy by hand or you make the Jenkins build task run the deploy task when it finishes without error.
One thing you might not be familiar with is Archiva/Maven's system of coordinates for each file.
Each artifact has a group, artifact id and version. There can be a classifier and such if you want.
- The group is typically, the company's domain name backwards plus internal taxonomy indicators -- com.microsoft.phone.web for a web app created by the phone division at microsoft.
- The artifact id is the name of a particular artifact.
- The version is a normal form of version string - 1.0a or 2.0-asl or 3.2.1.
- The classifier is used similar to the way we use file extensions - zip, jar.
This is the short version of this explained. Google is your friend here.
You can also use a Maven task to do this. The information on the Archiva page regarding the pom.xml file will be needed but you will have to Google "Maven deploy" and read how to do it for your particular case. The default case deploys when the artifacts are in the local Maven repo (on the build machine) and that repo has a specific file and folder structure that you need. That's the way Maven arranges artifacts when it creates and 'install's them.
