Robert Clipsham, el 14 de mayo a las 13:11 me escribiste: > Christopher Wright wrote: > >If dmd had public source control, we could set up continuous integration for > >it > >that will, for instance, run dstress and attempt to compile the latest > >release > >of various common libraries. Then Walter can just check its results when he > >wants to do a release -- depending on how long that takes to run. > > This is already done (to an extent) for ldc after each changeset at > http://ldc.buildbot.octarineparrot.com/ (note that this needs updating > to llvm /trunk, hence all the failures currently).
I can't access to this URL right now, it is really working? > If Walter is willing to put dmd under public source control I'd happily > set this up to automatically compile dmd, run tests suites, compile > libraries etc. I could even set up a one command/one click release > candidate/final release thing if needed (maybe even nightly builds too). That would be great. What would be the excuse not to do this? =) -- Leandro Lucarella (luca) | Blog colectivo: http://www.mazziblog.com.ar/blog/ ---------------------------------------------------------------------------- GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05) ----------------------------------------------------------------------------