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*
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
