The licenses on some of the tools may not cover having them in svn. If there were free open source versions that allowed redistributing the binaries of all the tools listed that did the job well, we could put them into svn.
However as far as I know there isn't a pure .net open source tool chain for some of the tools listed above. Thus it needs to be put on the slave or accessible from the slave with the limited licenses. Also one would want to install hudson plugins that generate reports and graphical information based on the xml documents generated during the build. Then have hudson process them on initial load and display them on the dashboard / build output. - Michael On Thu, Mar 3, 2011 at 1:57 PM, Wyatt Barnett <[email protected]>wrote: > I'd ask if we need to install this stuff on hudson at all -- most of > it is command line utilites that can be transported with the source in > svn anyhow. Sidebar advantages here are it is much easier to debug the > build scrips since you have no environmental dependencies and you've > got all the toys in one download. > > On Thu, Mar 3, 2011 at 10:05 AM, Michael Herndon <[email protected]> > wrote: > > Sorry I've been just reading through the list & wiki ( > > http://wiki.apache.org/general/Hudson) > > > > I subscribed to the list last night and haven't received the usual > message > > for activating subscriptions, I'll try again today and get on the list to > > see what is already on the windows slave. > > > > We also have to ask if others are interested in tools that not installed > and > > if not install them under home/username. > > > > - michael. > > > > On Wed, Mar 2, 2011 at 5:19 PM, Troy Howard <[email protected]> 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 <[email protected]> > wrote: > >> > +1 > >> > > >> > Scott > >> > > >> > On Mon, Feb 28, 2011 at 5:18 AM, Stefan Bodewig <[email protected]> > >> 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 > >> >> > >> > > >> > > > -- Michael Herndon Senior Developer ([email protected]) 804.767.0083 [connect online] http://www.opensourceconnections.com http://www.amptools.net http://www.linkedin.com/pub/michael-herndon/4/893/23 http://www.facebook.com/amptools.net http://www.twitter.com/amptools-net
