Oops Sorry I misread above mail. :D. For non buildable (as I mentioned it's in the apptype definition) if we are not showing build button we should not show the build no as well. And for deployed build ID we can show something else.
Thanks & Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Tue, Mar 3, 2015 at 2:08 PM, Gayan Dhanushka <gay...@wso2.com> wrote: > Hi Danushka, > > This is only for the non buildable application type artifacts. We can > continue to show the build id for the buildable application artifacts. > Hence the consistency issue. > > Regards > Gayan > > On Tue, Mar 3, 2015 at 1:59 PM, Danushka Fernando <danush...@wso2.com> > wrote: > >> Hi Gayan >> IMO its something nice to have. But with that there could be more >> complexities about what to show to user since we are showing which build id >> is deployed. On the other hand we could always increase build id in DB if >> build system doesn't give it. >> >> Thanks & Regards >> Danushka Fernando >> Software Engineer >> WSO2 inc. http://wso2.com/ >> Mobile : +94716332729 >> >> On Tue, Mar 3, 2015 at 1:52 PM, Gayan Dhanushka <gay...@wso2.com> wrote: >> >>> Hi all, >>> >>> Suppose we move away from the Jenkins freestyle builds that we are >>> triggering currently. Then we will not have a build number anyway. In that >>> case we need to have an alternative approach. One would be to show the last >>> deployed time since we already have that information in the AF_DEPLOY table >>> in the runtime database. >>> >>> Then again this would affect the consistency of the user experience. >>> >>> WDYT ? >>> >>> Regards >>> Gayan >>> >>> On Fri, Feb 27, 2015 at 8:25 PM, Gayan Dhanushka <gay...@wso2.com> >>> wrote: >>> >>>> Hi Danushka, >>>> >>>> There is an attribute already called isBuildable. As I noticed the >>>> deployment information is now shown for non buildable application types but >>>> we are showing the build id (build id generated from the free style jenkins >>>> build). IMO this is incorrect since the build id would mislead the user. So >>>> I am +1 for having something like Manisha has mentioned. >>>> >>>> WDYT? >>>> >>>> Regards >>>> Gayan >>>> >>>> On Fri, Feb 27, 2015 at 6:58 PM, Danushka Fernando <danush...@wso2.com> >>>> wrote: >>>> >>>>> Hi Gayan >>>>> IMO we should have some configuration like buildable (AFAIR we already >>>>> have this) in apptype and according to that we should draw the build >>>>> section. >>>>> >>>>> Thanks & Regards >>>>> Danushka Fernando >>>>> Software Engineer >>>>> WSO2 inc. http://wso2.com/ >>>>> Mobile : +94716332729 >>>>> >>>>> On Fri, Feb 27, 2015 at 4:34 PM, Gayan Dhanushka <gay...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> I am working on [1] and the I got some things to clarify. For >>>>>> apptypes with the build having a meaning (java web app, jaxrs, jaxws) we >>>>>> show a last build id,status and last deployed build id on the UI. But for >>>>>> jaggery applications in which we do not trigger an actual build, it does >>>>>> not make much sense to show the last build id (currently there is no wall >>>>>> message for a jaggery build as well). Showing the "Build ${id} Deployed" >>>>>> is >>>>>> also misleading. But when a user does some change in the application and >>>>>> commit it there should be some kind of a message for the user to >>>>>> understand >>>>>> whether his changes are there in the currently deployed version of the >>>>>> application as well. >>>>>> >>>>>> What would be the appropriate thing to do in here? >>>>>> >>>>>> [1] https://wso2.org/jira/browse/APPFAC-2978 >>>>>> >>>>>> Regards >>>>>> Gayan >>>>>> >>>>>> 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 >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> 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 >>>> >>> >>> >>> >>> -- >>> 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 >>> >> >> > > > -- > 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 >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
