Gayan, Indeed, looks like Udara and I are thinking along the same lines. :) This is more than just a build. E.g. when I am creating an application, there are a lot of things that happen (borrowing from your list):
1. application creation started 2. initial git repo creation 3. jenkins space creation 4. issue tracker space creation 5. app authorization in cloud environments 6. application creation completed If I am creating an app - I'd like to see them all - because this takes the mystery out of the process and makes me more comfortable with the platform. If my team-member is creating an app - these 6 events and their progress are just noise. All I need to do is: "Jane created a new Java app HelloWorld" (if my role allows me to even know that this new app exists). Again, obviously this all can be phase two. Dmitry On Tue, Aug 12, 2014 at 1:07 PM, Gayan Dhanushka <[email protected]> wrote: > Hi Dmitry, > > Thanks for pointing things out. IMO that would be phase two Dmitry. As > soon as I complete publishing all the relevant events I will look to > accommodate the noise-reduction filter as well. WDYT of the suggestion made > by Udara in the above reply? I think that is a valid comment as well. > > Hi Udara, > > The point that you are making is valid I think. With the suggestion made > by Dmitry in the above reply I think this will come into the picture. > > Thanks > GayanD > > > On Tue, Aug 12, 2014 at 2:27 PM, Udara Rathnayake <[email protected]> wrote: > >> Hi Gayan, >> >> See my comment in-line. >> >> On Tue, Aug 12, 2014 at 1:54 PM, Gayan Dhanushka <[email protected]> wrote: >> >>> Hi all, >>> >>> We have identified that the events in the doc attached herewith are the >>> events which are triggered within each page. While some of them are already >>> published, some of them needs to be published to the social component in >>> order to enhance the user experience and collaboration. While doing this we >>> have encountered some issues and some resolutions are proposed to overcome >>> those issues. >>> >>> *Problem*: There is no way to track whether a certain build or a >>> deployment instance triggered by someone is completed.(No association >>> between start and finish events for a certain instance). There is no way to >>> represent an ongoing process. (e.g. application creation in progress, build >>> is in progress etc.) >>> >> Here we have to think about the user experience. >> IMO the user who triggered the build only interested to see the progress >> of that particular build, others may be interested to see the start and the >> end but not the progress. >> >> WDYT? >> >>> >>> The same problem would be applied to any scenario where it takes some >>> time for a certain event to finish and app factory needs to capture both >>> start and completion events related to a particular instance. >>> >>> *Solution* : Use a UUID to track events which takes time to complete >>> >>> Publishing both start and complete events with the same UUID as a event >>> property would solve the problem. Then by looking at the event content we >>> are able to find whether there is a completion event for a certain start >>> event. This would be a global thing so the notification wall logic can be >>> written in such a manner that we need to have a look at only the UUID. If >>> we use different mechanisms for tracking start and completion events of >>> different events the notification wall logic would be more complex when >>> filtering out the events >>> >>> Your thoughts are welcome. >>> >>> [1] https://redmine.wso2.com/issues/3065 >>> >>> Thanks >>> GayanD >>> >>> -- >>> 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 >>> >>> >> >> >> -- >> *Udara Rathnayake* >> Software Engineer >> WSO2 Inc. : http://wso2.com >> >> Mobile : +94 772207239 >> Twitter : http://twitter.com/udarakr >> Blog : http://udarakr.blogspot.com >> >> >> _______________________________________________ >> 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 > > -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: [email protected]; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware <http://wso2.com/events/>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
