Hi, Same as Application creation process, I encountered that we should rollback the process with the application version creation or folking when it fail. Because In these cases, we create repo in git, version in issue tracker, job in jenkins and update registry about application info.
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 Sat, Jan 11, 2014 at 10:05 AM, Udara Liyanage <[email protected]> wrote: > From a perspective of user I like to see this as a set of process and if > one process is not successful,that perticular process should be able to > retry rather than aborting the whole process. User should be informed of > the process which is failed. If retry of a failed process(a mandatory > process) is not successful, a user should be able to abort the whole > process when he feels further retrying won't be successful. Additionally it > is better IMO if user can be showed whether the process is mandatory or > not, if not mandatory user should be able to Skipp and progress. > > Touched, not typed. Erroneous words are a feature, not a typo. > > _______________________________________________ > 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
