CI history

  • #68Jan 10, 2017David Fetter
  • #67Jan 10, 2017David Fetter
  • #64Jan 09, 2017David Fetter
  • #62Jan 05, 2017David Fetter
  • #61Jan 05, 2017David Fetter
  • #56Jan 01, 2017David Fetter
  • #47Sep 30, 2016Thomas Munro
  • #46Sep 29, 2016David Fetter
  • #33Sep 19, 2016David Fetter
  • #22Jul 27, 2016David Fetter
  • #17Jul 22, 2016David Fetter
  • #1Jul 21, 2016David Fetter
  • #68Jan 10, 2017
    training_wheels_011.patch
  • #67Jan 10, 2017
    training_wheels_010.patch
  • #64Jan 09, 2017
    training_wheels_009.patch
  • #62Jan 05, 2017
    training_wheels_008.patch
  • #61Jan 05, 2017
    training_wheels_007.patch
  • #56Jan 01, 2017
    training_wheels_006.patch
  • #47Sep 30, 2016
    fix-regression-test.patch
    fix-docs.patch
    + 1 more
  • #46Sep 29, 2016
    training_wheels_005.patch
  • #33Sep 19, 2016
    training_wheels_004.patch
  • #22Jul 27, 2016
    training_wheels_003.patch
  • #17Jul 22, 2016
    training_wheels_002.patch
  • #1Jul 21, 2016
    training_wheels_001.patch

Beta feature Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.

appliesbuild failedCI history

Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:

git clone --branch t34956_68 https://github.com/hackorum-dev/postgres.git

In a checkout you already have, add the fork once:

git remote add hackorum https://github.com/hackorum-dev/postgres.git

then, for this patchset and every later one:

git fetch hackorum t34956_68 && git checkout t34956_68

Patchset v68 (message #68) is on t34956_68