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
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=yy
Hi Sachith,
One way is to pass myproxy credentials as system properties Java VM (i.e.
like -Dmyproxy.user=xxx -Dmyproxy.password=). 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
[
https://issues.apache.org/jira/browse/AIRAVATA-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860687#comment-13860687
]
Sachith Withana commented on AIRAVATA-944:
--
Hi Saminda,
Shall I create a docum
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
[
https://issues.apache.org/jira/browse/AIRAVATA-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shameera Rathnayaka updated AIRAVATA-970:
-
Attachment: AIRAVATA-970.patch
Hi Dev,
Please find the patch which show the In
