Add NiFi-Registry-0.2.0 support #67
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…sions Improved processor scheduling call to check if start was successful, changed test to component.state from status.run_status as it's more reliable Minor logging cleanups and changes Deprecated testing against NiFi-1.5.0, added testing against NiFi-Registry-0.2.0 Added pytest fixture cleanups for NiFi-Registry testing Renamed 'regress' to 'regress_nifi' for clarity when working with tests Finally realised that fixture ordering matters and cleaned up a few things Added default log control for tox run as a convenience
…sions Improved processor scheduling call to check if start was successful, changed test to component.state from status.run_status as it's more reliable Minor logging cleanups and changes Deprecated testing against NiFi-1.5.0, added testing against NiFi-Registry-0.2.0 Added pytest fixture cleanups for NiFi-Registry testing Renamed 'regress' to 'regress_nifi' for clarity when working with tests Finally realised that fixture ordering matters and cleaned up a few things Added default log control for tox run as a convenience
debugging travisci
…sions Improved processor scheduling call to check if start was successful, changed test to component.state from status.run_status as it's more reliable Minor logging cleanups and changes Deprecated testing against NiFi-1.5.0, added testing against NiFi-Registry-0.2.0 Added pytest fixture cleanups for NiFi-Registry testing Renamed 'regress' to 'regress_nifi' for clarity when working with tests Finally realised that fixture ordering matters and cleaned up a few things Added default log control for tox run as a convenience
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reworked pytest parametrization to support multiple nifi-registry versions
Improved processor scheduling call to check if start was successful, changed test to component.state from status.run_status as it's more reliable
Minor logging cleanups and changes
Deprecated testing against NiFi-1.5.0, added testing against NiFi-Registry-0.2.0
Added pytest fixture cleanups for NiFi-Registry testing
Renamed 'regress' to 'regress_nifi' for clarity when working with tests
Finally realised that fixture ordering matters and cleaned up a few things
Added default log control for tox run as a convenience
Moved docker-compose to use explicit version numbers instead of latest to avoid inconsistent behavior