[ 
https://issues.apache.org/jira/browse/IGNITE-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644079#comment-14644079
 ] 

Dmitriy Setrakyan edited comment on IGNITE-1160 at 7/28/15 8:45 AM:
--------------------------------------------------------------------

Cos, I think many people would find it a lot more convenient to simply change 
code and have that code automatically deploy, instead of going through manual 
step of building an artifact themselves. I like support for VCS repositories.


was (Author: dsetrakyan):
Cos, I think many people would find it a lot more convenient to simply change 
code and have that code automatically deploy, instead of going through manual 
step of building an artifact themselves.

> Ignite.deploy(...) method to automatically deploy user code and libraries
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-1160
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1160
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>            Reporter: Dmitriy Setrakyan
>             Fix For: sprint-9
>
>
> Implement {{Ignite.deploy(...}} method to automatically deploy user code and 
> libraries on all Ignite server nodes.
> The method should accept the following parameters:
> # A collection of URIs to get user archives from (ZIPs and JARs should be 
> handled.
> # A collection of GIT repositories with a POM file
> # A collection of Maven artifacts and Maven repositories.
> We should also add {{-deploy}} option to the {{ignite.sh}} script should 
> should start a client node and automatically deploy the specified artifacts 
> (supporting all the options listed above)
> The process should be as follows:
> # start as many server nodes as needed.
> # start a client node, call {{deploy(...)}} and then start using the client.
> # alternatively, call {{ignite.sh -deploy}} to deploy code on the servers, 
> before starting using Ignite. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to