Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master
Commits on Jan 21, 2011
  1. Allow overriding branches.sh by providing a branches-local script.

    Tommi Virtanen authored
    This lets users configure gitbuilder without needing to change any
    files tracked by git.
    
    Note that branches.sh still chdirs to the build directory, as a
    convenience.
Commits on Sep 24, 2009
  1. results page: skip branches with '@' in their name.

    authored
    These branches are generally just weird interim tags created by git-svn, and
    they're not interesting to look at.
Commits on Sep 15, 2009
  1. We'd better specify exactly what the license applies to.

    authored
    Tacked it on to the beginning of LICENSE.
Commits on Apr 29, 2009
  1. README: gitbuilder doesn't "update itself automatically"

    authored
    It can build your software automatically.  Which is updating in a sense, but
    not an obvious sense :)
    
    (Thanks to Josef Wolf for pointing this out.)^
Commits on Apr 18, 2009
  1. log.cgi: display blank lines correctly.

    authored
    Log files are really confusing without their blank lines!
Commits on Dec 12, 2008
  1. Merge /home/eduardo/gitbuilder

    authored
    * /home/eduardo/gitbuilder:
      Add support for forcing rebuild
  2. run-build.sh: run 'git checkout .' first to get rid of funny-looking …

    authored
    …warnings.
    
    The "git reset --hard" that came after compensated for problems caused by
    modified files anyway, but the output looked confusing.
  3. Add support for forcing rebuild

    eduardo authored
    (Force Rebuild) is now shown at the right, for FAILED builds.
Commits on Dec 9, 2008
  1. run-build.sh: run "git clean" with the -q flag.

    authored
    I'm pretty confident it's working nowadays, and all the notifications about
    deleted files were cluttering the log.
Commits on Nov 14, 2008
  1. changelog-email: add MIME-Version header.

    authored
    Without this, Microsoft Exchange seems to do *really* weird things to your
    messages, including auto-uuencoding them.  Whee!  Anyway, it's technically
    incorrect to leave out that header.
Commits on Oct 29, 2008
  1. index.cgi: fix a warning.

    authored
  2. Oops, cache didn't properly handle silent errors caused by the error …

    authored
    …code.
    
    If the build failed and returned nonzero but didn't print an error, the
    caching would result in us printing 'ok' instead of reporting an error.
  3. Cache the results of log parsing.

    authored
    Greatly speeds up generating the index.cgi and rss.cgi output after the
    first time.
  4. Some whitespace fixups.

    authored
Commits on Oct 21, 2008
Commits on Oct 20, 2008
  1. Add and use 'runtee' to avoid hangs due to long-running subprocesses.

    authored
    If build.sh ended up launching a daemon or other program that ran in the
    background, the autobuild cycle would hang, because that daemon might keep
    its stdout open, and thus the "tee" it was feeding into would never exit.
    
    Of course, daemons are supposed to close their stdout/stderr when forking
    into the background, for exactly this reason.  But since we're an
    autobuilder, we have no guarantee that the daemons we end up launching are
    actually well-written and bug free, so we can't rely on this working.
    
    Instead, runtee exits as soon as its subprogram dies *and* the input pipe
    is empty.  It doesn't wait for the input pipe to *close*, however.
Commits on Oct 17, 2008
  1. build.sh.example: show how to use the 'maxtime' script for tests.

    authored
    I had almost forgot I wrote maxtime.  Man, I'm awesome.
  2. Don't forget to "git remote prune".

    authored
    Otherwise deleted branches that were removed from the origin won't disappear
    from the autobuilder.  I appreciate that "git remote update" never
    auto-deletes branches, but that safety seems unnecessary in the autobuilder.
  3. Remove an erroneous "grep -v" from run-build.sh.

    authored
    This was used for testing earlier, but accidentally removed certain lines
    from the log files.  Oops!
  4. Include "pending" branches in Most Recent list too.

    authored
    This involved fixing a bug in the newly introduced "branches.sh -v", where
    the listed tags weren't actually the commitid of the tag, but the tag's hash
    instead.
Commits on Oct 16, 2008
  1. Include the actual count of warnings/errors/failures.

    authored
    Since we have that number available, actually print it out.  It can be
    useful to indicate trends of improvement/degradation.
  2. Ignore warnings between --START-IGNORE-WARNINGS and --STOP-IGNORE-WAR…

    authored
    …NINGS.
    
    This allows you to mark parts of your build output as "warning-free", which
    is useful when you include modules that are out of your control.
  3. index.cgi: entries with warnings are now yellow, not green.

    authored
    Also moved the hardcoded colour formatting out to index.css.
  4. Correctly report Warnings vs. Errors vs. Failures.

    authored
    The previous logic would misreport the sort of problem depending on the
    script's exit code.  Now we always report Warnings, Errors, and Failures
    separately when we find them, *and* force an error if the exit code was
    nonzero *and* there were no test failures (since a build error is the only
    reason such a thing should happen).
    
    The result is we can now see at a glance when a build fails because of unit
    tests vs. build failures.
  5. index.cgi: Removed experiments with "hover" attributes, etc.

    authored
    They mostly just made the UI less obvious, instead of more obvious.  Just
    make hyperlinks work like normal instead of trying to be fancy.
Something went wrong with that request. Please try again.