response from build list:
On Thu, Mar 3, 2011 at 7:55 PM, Michael Herndon <mhern...@wickedsoftware.net> wrote: > Also does anyone know of the existing tools that maybe available on the > windows slave such as: > ncover, > ndepend, > fxcop, > msbuild, > versions of the .net framework > etc. > (If these does not already exist on the server, we would like to request > licenses for opensource projects for both ncover & ndepend) Sorry, our documentation for what we got installed on the different slaves is not kept up to date :-/ Anyways, we got .Net 2.0, 3.5 and 4.0 installed on the Windows slave. As for the other tools, please open JIRA issues and I'll take care of them. Also, if you could assist in requesting the needed licenses, that would be great. > Which version of the OS is installed on the windows salve? Windows Server Standard 2008, Service Pack 2. > Would it be possible to also setup a mono build on a linux slave? Yes. Requested additionally needed packages if needed On Wed, Mar 2, 2011 at 5:19 PM, Troy Howard <thowar...@gmail.com> wrote: > I've been following builds@ for the past couple of days. Looks like > they just finished the migration to Jenkins. > > Michael - Have you had a chance to contact them and find out what > tools are available out of our list? Want me to do that? > > Thanks, > Troy > > On Mon, Feb 28, 2011 at 9:19 PM, Scott Lombard <slomb...@theta.net> wrote: >> +1 >> >> Scott >> >> On Mon, Feb 28, 2011 at 5:18 AM, Stefan Bodewig <bode...@apache.org> wrote: >> >>> On 2011-02-28, Troy Howard wrote: >>> >>> > One quick concern I have, is how much of the things listed are already >>> > available on the Apache hudson server? >>> >>> builds@apache is the place to ask. >>> >>> > A lot of this is .NET specific, so unlikely that it will already be >>> > available. >>> >>> well, the DotCMIS build seems to be using Sandcastle Helpfile Builder by >>> looking the console output. >>> >>> > We'll have to request that ASF Infra team install these tools for us, >>> > and they may not agree, or there might be licensing issues, etc.. Not >>> > sure. I'd start the conversation with them now to suss this out. >>> >>> Really, go to the builds list. License issues usually don't show up for >>> build tools. It may be good if anybody of the team could volunteer time >>> helping administrate the Windows slave. >>> >>> > - Mono is going to be a requirement moving forward >>> >>> This could be done on a non-Windows slave just to completely sure it >>> works. This may require installing a newer Mono (or just pulling in in >>> a different Debian package source for Mono) than is installed by >>> default. >>> >>> > - Project structure was being discussed on the LUCENENET-377 thread. >>> >>> As a quick note, in general we prefer the mailing list of JIRA for >>> discussions around the ASF. >>> >>> Stefan >>> >> >
