CI history

  • #38Apr 04, 2017vinayak
  • #34Mar 29, 2017vinayak
  • #32Mar 24, 2017vinayak
  • #30Mar 22, 2017vinayak
  • #28Mar 21, 2017vinayak
  • #24Mar 17, 2017vinayak
  • #17Mar 10, 2017vinayak
  • #1Feb 28, 2017vinayak
  • #38Apr 04, 2017
    pg_stat_progress_analyze_v8.patch
  • #34Mar 29, 2017
    pg_stat_progress_analyze_v7.patch
  • #32Mar 24, 2017
    pg_stat_progress_analyze_v6.patch
  • #30Mar 22, 2017
    pg_stat_progress_analyze_v5.patch
  • #28Mar 21, 2017
    pg_stat_progress_analyze_v4.patch
  • #24Mar 17, 2017
    pg_stat_progress_analyze_v3.patch
  • #17Mar 10, 2017
    pg_stat_progress_analyze_v2.patch
  • #1Feb 28, 2017
    pg_stat_progress_analyze_v1.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.

won't retrybuild 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 t36145_38 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 t36145_38 && git checkout t36145_38

Patchset v38 (message #38) is on t36145_38