I like the notification idea, vincent, and by setting the threshold to high on that profile, I presume notifications would only occur for bugs that are likely to be 'real' issues.
I still do think it would be useful to have the site deployed through hudson, so people can access the QA reports at any given time. Regarding the doc space, I don't know, how do other apache projects manage this? Cheers, Chico 2009/2/20 Vincent Siveton <[email protected]> > Hi Chico, > > mmmh an automated deployment for the site seems to be a good idea at > the first read but... few developers looks at Hudson *regularly* so I > guess it should be the same for the automated site. > > The site actually contains the project info reports and if running > with reporting profile, it will contain Javadocs and some QA reports. > So site is useful only for QA reports. > > Instead of automated deployment, we could create a QA profile with > failOnError = true for wanted QA plugins. If we have a notifications @ > for Hudson, we could receive QA errors then devs could have a glance > on pb. > > Also, IMHO we will lost the user with this new doc space in addition > to the official website (not really up to date) and 2 wikis. > > Cheers, > > Vincent > > 2009/2/20, chico charlesworth <[email protected]>: > > I think it would be really useful to get this up n running in an > automated > > fashion .. > > > > I ran findbugs (through the eclipse plug-in) and it found a few things > w/ > > each of the modules. For example, the following HTTP splitting > vulnerability > > was found on line 64 of ConcatProxyServlet in the gadgets module: > > - "This code directly writes an HTTP parameter to an HTTP header, which > > allows for a HTTP response splitting vulnerability. See > > http://en.wikipedia.org/wiki/HTTP_response_splitting for more > information." > > > > I'm not an expert on HTTP vulnerabilities, but I like the fact that > findbugs > > highlighted this .. > > > > I think it would be useful to have the shindig site deployed as part of > the > > automated build process, so that the community has visibility to these > > 'potential' issues. And other great features like code coverage and the > TODO > > tag list also warrants having this :) > > > > Cheers > > Chico > > > > 2009/2/19 Ian Boston <[email protected]> > > > > > I have been deploying it at > > http://people.apache.org/~ieb/shindig<http://people.apache.org/%7Eieb/shindig> > <http://people.apache.org/%7Eieb/shindig> > > > > > > > > but I have done this manually since I couldn't get cron to work on > people > > > (probably because I should not be using it :)) > > > > > > It would be nice to have a hudson job to do it, but I am not certain > how it > > > would deploy from there. > > > Ian > > > > > > > > > > > > On 19 Feb 2009, at 16:21, chico charlesworth wrote: > > > > > > Hi all, > > >> > > >> Is 'mvn site' being run for shindig? If so, does anyone know where > the > > >> site > > >> is being deployed to? > > >> > > >> Cheers > > >> Chico > > >> > > > > > > > > >
