Hi, We have another approach to do this. We can copy the repository as it is from repository-git to s2-git from server to server without doing check out to local folder it appfactory. When promote that, we can do the same thing. But when we demote it, we have to check out the artifact from s2-git to local folder in appfactory, delete it and push it again.
@ashansa, yes we have auto deployment feature. To un-buildable artifact we can auto-deploy when commit is triggered to git. Current impl, git notify to jenkins when commit comes. Now we have to get it in to appfactoy and check whether it is buildable or not and decide which deployment strategy should apply. What is best approach to do this ? WDYT ? thanks *Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * <http://www.apache.org/>* * email: **[email protected]* <[email protected]>* cell: +94 71 5186770* * twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>* *harshathirimann linked-in: **http: <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>* *Lean . Enterprise . Middleware* On Tue, Nov 12, 2013 at 5:02 PM, Ashansa Perera <[email protected]> wrote: > Hi Harsha, > > It would be good to disconnect the app types which should not be buildable > from the build server since it is a valid scenario that people do not want > to have a build server if they need only some application types which does > not need to be built. > But there are few concerns regarding this > 1. What is our approach for auto deploy? ( we obviously do not need auto > build, but IMO we cannot remove auto deploy feature ) > 2. Are we going to manage a separate cloning folder in AF or are we going > to clone the full app in each time we need to do a deploy? > > > On Tue, Nov 12, 2013 at 2:49 PM, Harsha Thirimanna <[email protected]>wrote: > >> Hi, >> >> We have few artifact type that shouldn't want to build like Jaggery, PHP. >> So customer will not accept to start separate build server without having >> such a requirement. Because of that we thought to handle this deployment >> from appfactoy. >> >> Just checkout the repository to appfactory local folder and push to the >> s2-git from that. In this case when do promoting , we have to copy this >> appfactory local repository folder to relevant stage local folder and >> commit to s2-git for that stage. >> >> We have to identify the non-buildable artifact through appfactory and >> remove build option, build status, build log and some feature that can be >> come to buildable artifact in future. It is possible to put some >> identification for artifact type in appfactory configuration. >> >> WDYT ? >> >> *Harsha Thirimanna* >> Senior Software Engineer; WSO2, Inc.; http://wso2.com >> * <http://www.apache.org/>* >> * email: **[email protected]* <[email protected]>* cell: +94 71 5186770* >> * twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>* >> *harshathirimann linked-in: **http: >> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 >> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>* >> >> *Lean . Enterprise . Middleware* >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Thanks & Regards, > > Ashansa Perera > Software Engineer > WSO2, Inc > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
