Re: [Lustre-discuss] Landing and tracking tools improvements

2011-05-24 Thread sebastien . buisson
work! Cheers, Sebastien. lustre-discuss-boun...@lists.lustre.org a écrit sur 23/05/2011 19:06:40 : De : Chris Gearing ch...@whamcloud.com A : lustre-discuss@lists.lustre.org Date : 23/05/2011 19:06 Objet : [Lustre-discuss] Landing and tracking tools improvements Envoyé par : lustre-discuss

Re: [Lustre-discuss] Landing and tracking tools improvements

2011-05-24 Thread Andreas Dilger
I have to echo some of the comments of Chris Morrone. The in-line comments in Gerrit do not appear in the expanded view, and need to be found individually in the various patches. Having 3 lines of context plus the comments is enough for most cases, and if not then a URL to the actual comment

[Lustre-discuss] Landing and tracking tools improvements

2011-05-23 Thread Chris Gearing
We now have a whole kit of tools [Jira, Gerrit, Jenkins and Maloo] used for tracking, reviewing and testing of code that are being used for the development of Lustre. A lot of time has been spent integrating and connecting them appropriately but as with anything the key is to continuously look

Re: [Lustre-discuss] Landing and tracking tools improvements

2011-05-23 Thread Christopher J. Morrone
My biggest complaint is that discussion about an issue and its associated patch(es) is scattered about in multiple locations instead of located in a single bug like with bugzilla. Here is a list of things I have had trouble with: - jira: There is no clue in the jira ticket that the

Re: [Lustre-discuss] Landing and tracking tools improvements

2011-05-23 Thread Liang Zhen
A small suggestion about Maloo: I think It would be helpful if we can sort testing results by base branch, I actually can't find branch information even after clicking into result report. Thanks Liang On May 24, 2011, at 1:06 AM, Chris Gearing wrote: We now have a whole kit of tools [Jira,