Yes. I too agree on that. So with the forked repos, we need to delete build jobs of the forked repos too. There are no complications that I found as of now.
Anyway, we thought of not implementing into this release. Hence added a RM so we can push it as a proper feature into post 2.1.0 release Thanks Manisha On Tue, Mar 3, 2015 at 1:51 PM, Danushka Fernando <[email protected]> wrote: > Hi Manisha > IMO it should be deleted. What are the complications in deleting them. > Even the deployed artifacts also should be deleted. > > Thanks & Regards > Danushka Fernando > Software Engineer > WSO2 inc. http://wso2.com/ > Mobile : +94716332729 > > On Tue, Mar 3, 2015 at 12:41 PM, Gayan Dhanushka <[email protected]> wrote: > >> Hi Manisha, >> >> Since this is a private repository (inside the tenant) IMO all the fork >> repositories and the build jobs should be deleted. Anyways there is no >> point of having a forked repository without a parent. If the user wants to >> retain the code, the local copies can be retained. >> >> It would be good to publish this information to the user wall to notify >> the users involved in the application. >> >> Regards >> Gayan >> >> On Mon, Mar 2, 2015 at 2:31 PM, Manisha Gayathri <[email protected]> >> wrote: >> >>> Hi all, >>> >>> I am working on [1] >>> Basically the user story is as below: >>> >>> 1. App owner creates an application >>> 2. Invites few developers (dev1,dev2...) to the app >>> 3. They fork the main repo and create individual repos for them >>> 4. App owner deletes the application. This should automatically >>> delete: >>> - Parent repo in git >>> - Build job in jenkins >>> - Issue tracker space >>> - Forked repos of dev1, dev2,... >>> - Build jobs of forked repos of dev1, dev2... >>> >>> The user story is partially complete with current AF, except for the >>> above 2 red highlighted functionalities. >>> >>> What would be the proper user story for deleting forked repos and >>> respective build jobs? >>> We can leave the forked repos as it is, even though the parent >>> application (eg: app1) is deleted because forked repos are developers' >>> personal space. >>> But on the other hand, if we leave the forked repos without deleting >>> when the app1 is deleted, we face an issue. >>> That is, say someone creates a new app with app1 again and invites dev1. >>> Dev1's UI does not show any forked repos. Only the parent repo of new app1 >>> is shown. If dev1 tries to fork app1 again, it will give an error saying >>> that he already has a fork. >>> >>> >>> So how should we handle this requirement? >>> >>> Thanks >>> Manisha >>> >>> [1]. https://wso2.org/jira/browse/APPFAC-2226 >>> >>> -- >>> ~Regards >>> *Manisha Eleperuma* >>> Software Engineer >>> WSO2, Inc.: http://wso2.com >>> lean.enterprise.middleware >>> >>> *blog: http://manisha-eleperuma.blogspot.com/ >>> <http://manisha-eleperuma.blogspot.com/>* >>> *mobile: +94 71 8279777 <%2B94%2071%208279777>* >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Gayan Dhanuska >> Software Engineer >> http://wso2.com/ >> Lean Enterprise Middleware >> >> Mobile >> 071 666 2327 >> >> Office >> Tel : 94 11 214 5345 >> Fax : 94 11 214 5300 >> >> Twitter : https://twitter.com/gayanlggd >> >> _______________________________________________ >> 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 > > -- ~Regards *Manisha Eleperuma* Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware *blog: http://manisha-eleperuma.blogspot.com/ <http://manisha-eleperuma.blogspot.com/>* *mobile: +94 71 8279777 <%2B94%2071%208279777>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
