Mailing-List: contact users-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@archiva.apache.org
MIME-Version: 1.0
In-Reply-To: <017701d03671$f91ce850$eb56b8f0$@nuearth.com>
References: <017701d03671$f91ce850$eb56b8f0$@nuearth.com>
From: Olivier Lamy <olamy@apache.org>
Date: Fri, 23 Jan 2015 10:06:16 +1100
Message-ID: 
 <CAPoyBqQj9feG0iY+eWnzRFfGGQA-JHNba8X2EpsLpaBhCH+9MA@mail.gmail.com>
Subject: Re: Jenkins deployment from Archiva
To: users@archiva.apache.org
Content-Type: multipart/alternative; boundary=089e0160b8a64d76ca050d45b971

--089e0160b8a64d76ca050d45b971
Content-Type: text/plain; charset=UTF-8

Hi,
If you use the Maven Job type with Jenkins you can activate the post build
step to deploy to Archiva ("Deploy artifacts to Maven repository").
Note you will have to store username/password within Jenkins to deploy to
Archiva.
I recommend you use the plugin ConfigFileProvider to store and share
between jobs.


On 23 January 2015 at 05:33, Malcolm G. Davis <malcolm@nuearth.com> wrote:

> I would like to create Jenkins job that deploys a war from Archiva.
>
> Is there a specific Jenkins steps or Maven configuration that will read a
> war from Archiva and deploy to an application server?
>
> I know many want to auto-deploy after a successful build, but there are
> internal QA steps that need to be followed, and there is tracking and
> sign-off that needs to occur.   The war is required to deploy from Archiva.
>
> Thanks,
> Malcolm
>
>


-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

--089e0160b8a64d76ca050d45b971--