updatecheck demo - DO NOT COMMIT #123
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a demonstration of a working updatecheck target.
That target works by pulling down UPGRADE_FROM version of pgtap via pgxn (currently defaults to 0.94.0), installing the current version, and then doing
then running the unit tests.
The other big change in here is that all installcheck activity is now managed with pg_regress execution schedules. There are two big wins from that:
To support that, there's now a test/build directory where temporary build objects are put.
If we're happy with this code then I'll get it into master and start hammering out the remaining upgrade issues.