CI history

  • #34Mar 08, 2018Masahiko Sawada
  • #20Aug 17, 2017Masahiko Sawada
  • #1Jul 07, 2017Petr Jelinek
  • #34Mar 08, 2018
    0001-Improve-messaging-during-logical-replication-worker-_v3.patch
  • #20Aug 17, 2017
    0001-Improve-messaging-during-logical-replication-worker-_v2.patch
    0002-Split-the-SetSubscriptionRelState-function-into-two_v2.patch
    + 2 more
  • #1Jul 07, 2017
    0001-Improve-messaging-during-logical-replication-worker-.patch
    0002-Exit-in-sync-worker-if-relation-was-removed-during-s.patch
    + 4 more

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 t37068_34 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 t37068_34 && git checkout t37068_34

Patchset v34 (message #34) is on t37068_34