Hi Shamika, In this case, do we restrict exposing repository URL to user to checkout/checkin this artifact ? Because even though we not show this URL in AppFactory UI , user can see this after login to the Git server.
thanks *Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * <http://www.apache.org/>* * email: **hars...@wso2.com* <az...@wso2.com>* 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 Mon, Jan 6, 2014 at 4:43 PM, Shamika Ariyawansa <sham...@wso2.com> wrote: > Hi All, > > New feature that is going to be introduced to AppFactory is creating a new > application by uploading exiting binary file of an application. e.g WAR > > *User Scenario* > > 1. User logs on to the system, goes to the application creation page. > 2. In there user provides basic information related to the application, > such as name, key, description then he/she would be able to create the > application by choosing one of the following options, > > a. Create the application from the scratch by selecting the repository > type and application type which maps with existing functionality. *OR* > b. Create the application by uploading the binary file and selecting the > binary file type. By doing so the application will be created as > non build-able application. > > 3. In "Repos and Builds" page user will be able to see the > uploaded application and he/she will be able to do following operations > from there, > a. Delete the existing application. > b. Upload new version of the same application. - Provides a way to > upload new binary file. > c. Test the application by deploying to Dev cloud. > > Note that for applications created like this, source repository paths, > build options and not shown to the users. > > 4. From Life Cycle Management page user will be able to Promote and Demote > the application through different life cycles. > > *Solution* > > So far in AppFactory we maintain two logical types of application flows. > Buildable and non-Buildable. Buildabale applications are mainly handled > and deployed by the buildserver (Jenkins) whereas non-Buildable are > maintained and deployed by the AppFactory itself. > uploading existing application functionality will > be implemented considering Non-Buildable application flow as follows. > > [image: Inline image 2] > > Further App Creation, Build and Repos and other UIs will > be changed accordingly. > > > Regards, > -- > Shamika Ariyawansa > Senior Software Engineer > WSO2, Inc.; http://wso2.com > > LK - +94 7639629 Ext 5999 > US - +1 408 754 7388 Ext 51732 > Mob:+ 94 772929486 > > *twitter: > **https://twitter.com/Amila_Shamika*<https://twitter.com/Amila_Shamika> > * linked-in: *http://www.linkedin.com/pub/dir/Shamika/Ariyawansa > > *Lean . Enterprise . Middleware* >
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
