If you go to http://drdr.racket-lang.org/current
then you will get redirected to the current one. This shell script: curl -I http://drdr.racket-lang.org/current | grep Location | awk -F/ '{print $2}' will give just that number... the Racket code would be simple too Jay On Fri, Aug 26, 2011 at 2:13 PM, Eli Barzilay <[email protected]> wrote: > Can you also add some quick file that has just the most recently done > push number? (Something that I can poll with minimal cost for the > drdr machine.) > > > About a minute ago, Jay McCarthy wrote: >> I've added >> >> http://drdr.racket-lang.org/builds/$PUSH/trunk.tgz >> >> for the last 100 builds (going forward) >> >> It's an archive of the git trunk after running 'make install'. >> >> Jay >> >> On Thu, Aug 25, 2011 at 3:06 PM, Eli Barzilay <[email protected]> wrote: >> > IIUC, after each drdr build, it generates the report pages, and then >> > it dumps the built tree. If so, how about changing it: before the >> > tree is removed, it archives the built files (run `git ls-files -o') >> > and makes the archive available somewhere. >> > >> > If this is done, then I can do the following: >> > >> > 1. Given that drdr is usually very busy, download new build archives >> > to someplace else (like pre.racket-lang.org) >> > >> > 2. Write some script that you'd run with `git pre-build', which would >> > check whether there's a build archive available for your current >> > HEAD. This means that after you've pulled new stuff into your >> > repo, you could just run this command and get a working tree very >> > quickly. >> > >> > 3. Even more: if there's no archive for your HEAD, it could check your >> > origin/master, and if that's part of your current HEAD history (as >> > happens after a `git pull --rebase'), it will still do that. This >> > means that you'd be left with a tree that has compiled results for >> > an older version, but with most uses of `pull --rebase', this means >> > that only files that you've worked on are outdated, so a followup >> > setup would usually be very quick. >> > >> > 4. Of course, that won't help with changes in src, and the script >> > could warn you about that. It also wouldn't help much if you have >> > edits in core files like in the `racket' collection. >> > >> > -- >> > ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: >> > http://barzilay.org/ Maze is Life! >> > _________________________________________________ >> > For list-related administrative tasks: >> > http://lists.racket-lang.org/listinfo/dev >> > >> >> >> >> -- >> Jay McCarthy <[email protected]> >> Assistant Professor / Brigham Young University >> http://faculty.cs.byu.edu/~jay >> >> "The glory of God is Intelligence" - D&C 93 > > -- > ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: > http://barzilay.org/ Maze is Life! > -- Jay McCarthy <[email protected]> Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay "The glory of God is Intelligence" - D&C 93 _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
