Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 719E810692 for ; Thu, 2 Jan 2014 21:49:18 +0000 (UTC) Received: (qmail 23841 invoked by uid 500); 2 Jan 2014 21:49:18 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 23805 invoked by uid 500); 2 Jan 2014 21:49:18 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 23798 invoked by uid 99); 2 Jan 2014 21:49:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jan 2014 21:49:18 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of thejaka.amila@gmail.com designates 209.85.219.47 as permitted sender) Received: from [209.85.219.47] (HELO mail-oa0-f47.google.com) (209.85.219.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jan 2014 21:49:11 +0000 Received: by mail-oa0-f47.google.com with SMTP id k1so15371986oag.34 for ; Thu, 02 Jan 2014 13:48:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=5/VhlPeJEBUAX55odCC/l0K72TKjz4NW2GncHKgJgqM=; b=ZotzSQ5de+2/Ic44Hd9GRFwPodOMym3tdQiwYGwcsSA3FAq2r/2s6L9rNVX/Cevbq5 HVPdZRyu/YSRKY6zyBkIwAiMSIvv/1MU+BsPhezolHR+N3fVK8V3m3QbsBWsnK9rgskd CF0GTuzTpTf4EdBHRTV6Zj+RNdKjV06j448bMGhYHlwrSaCsdzpnjEKeUXEKSj1b7pzf auO049Ls0alN2ZtsjlD2hF/Z9LvDwtMXY5HgqP0dyYNT+na3pqCbdWqKqQaJDgSgBqgs U1WQdEff6iFcOeY2TmYiYveWAN8B4BaH1SB+iDN8i7amZ+DhZ1aB7OYJXU8vhuFs4bUB n0+w== MIME-Version: 1.0 X-Received: by 10.182.28.134 with SMTP id b6mr56692277obh.27.1388699330217; Thu, 02 Jan 2014 13:48:50 -0800 (PST) Received: by 10.76.98.131 with HTTP; Thu, 2 Jan 2014 13:48:50 -0800 (PST) In-Reply-To: References: Date: Thu, 2 Jan 2014 16:48:50 -0500 Message-ID: Subject: Re: Integration test Jenkins integration From: Amila Jayasekara To: dev Content-Type: multipart/alternative; boundary=001a11c2903c470aca04ef03c2db X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2903c470aca04ef03c2db Content-Type: text/plain; charset=ISO-8859-1 One possibility is to add them to svn and refer from svn. But I am not sure whether this will work. Thanks Amila On Thu, Jan 2, 2014 at 3:29 PM, Sachith Withana wrote: > Thanks Amila. > > That's good. How can we configure the certificates? Only the admin can do > that right? > > > On Thu, Jan 2, 2014 at 3:26 PM, Amila Jayasekara wrote: > >> Hi Sachith, >> >> One way is to pass myproxy credentials as system properties Java VM (i.e. >> like -Dmyproxy.user=xxx -Dmyproxy.password=yyyy). This we have to do in the >> Jenkins build configurations. Further only admin will be able to access >> jenkins configurations, therefore I believe my proxy credentials will stay >> safe. >> >> Thanks >> Thejaka Amila >> >> >> On Thu, Jan 2, 2014 at 2:12 PM, Sachith Withana wrote: >> >>> Hi all, >>> >>> How can I allow the Jenkins build to test the integration tests for the >>> providers since the credentials and the certificates are needed? >>> >>> -- >>> Thanks, >>> Sachith Withana >>> >>> >> > > > -- > Thanks, > Sachith Withana > > --001a11c2903c470aca04ef03c2db Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
One possibility is to add them to svn and refer from svn. = But I am not sure whether this will work.

Thanks
Amila


On Thu, Jan 2, 2014 at 3:29 PM, Sachith Withana <swsachith@gmail.com= > wrote:
Thanks Amila.

That's good. How can = we configure the certificates? Only the admin can do that right?=A0


On Thu, Jan 2, 2014 at 3:26 PM, Amila Jayasekara <thejaka.amila@gmai= l.com> wrote:
Hi Sachith,

<= div>One way is to pass myproxy credentials as system properties Java VM (i.= e. like -Dmyproxy.user=3Dxxx -Dmyproxy.password=3Dyyyy). This we have to do= in the Jenkins build configurations. Further only admin will be able to ac= cess jenkins configurations, therefore I believe my proxy credentials will = stay safe.

Thanks
Thejaka Amila=A0
=


On Thu, Jan 2= , 2014 at 2:12 PM, Sachith Withana <swsachith@gmail.com> w= rote:
Hi all,

= How can I allow the Jenkins build to test the integration tests for the pro= viders since the credentials and the certificates are needed?=A0

--
Thanks,
Sachith Withana





<= /div>--
Thanks,
Sachith Withana
--001a11c2903c470aca04ef03c2db--