andreasscherbaum/buildfarm-client

PostgreSQL and Greenplum Buildfarm and Development client

buildfarm-client's Issues

Stop retrieving "/issues/" links from GitHub

The client right now happily processes "/issues/" links, and then fails with:

ERROR: Can't identify type of patch!

Move retrieving patches before cloning the repository

In case the build host has no network connection, or one of the patches can't be retrieved, there is no need to clone the repository.

Add script to run a single regression test

Pass the regression test name as argument, much like the psql script.

Add script for running bugbuster tests (Greenplum only)

Right now there is no script to run only the bugbuster test suite. Something similar to the following script might work:

#!/bin/sh


export PATH=/home/ads/postgresql/buildfarm/install/2016-08-18_103952_master/bin:$PATH
export PGPORT=15432

./pg_regress --psqldir=/home/ads/postgresql/buildfarm/install/2016-08-18_103952_master/tmp_regression_tests/qddir/demoDataDir-1 --schedule=./bugbuster/known_good_schedule --srcdir=./ --psqldir=/home/ads/postgresql/buildfarm/install/2016-08-18_103952_master/bin --inputdir=bugbuster

Show build data for "last" build

Right now, in order to show build data, one has to specify the build number. Add a --last-build option, or similar.

Make sure that it only affects manual builds, not buildfarm builds.

Store all build parameters in the database

Things like build dir, install dir and such should be stored in the local database. Listing a build should list this data, if available. Also have separate parameters to show a single value.