[SQOOP-3228] Add docker support to Sqoop test infrastructure to run third party tests automatically

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Vasas Szabolcs
• Created: 30/Aug/17 07:50
• Updated: 30/Aug/17 07:50

Description

Executing Sqoop third party tests is not a quick and easy task to do currently. It requires running instances of MySQL, MSSQL, Oracle EE, Cubrid and PostgreSQL database servers which makes it very hard for the contributors to verify their patches before submitting them and thus it increases the chance of introducing new bugs and regressions.
An idea to make this process easier is to use docker containers running the necessary database server instances and execute the Sqoop third party test suite against these instances. This would enable any contributor to fully verify the patches without installing 5 extra applications and we could also extend our CI system to run the third party test pack too.
This is an umbrella JIRA I created for the subtasks required to achieve these goals. If you have any suggestion please feel free to leave it in a comment.

Sub-Tasks

• Database credentials cannot be configured in PostgreSQL third party tests: Resolved
• Modify MySQLAuthTest to use configurable test database parameters: Resolved
• SQLServerDatatypeImportDelimitedFileTest can fail in some environments: Resolved
• ImportTest, ExportTest and TimestampDataTest fail because of column escaping problems: Resolved
• Document how to run third party tests manually with databases running in docker: Resolved
• Create test categories instead of test suites and naming conventions: Resolved
• Categorize all tests in the project: Resolved
• Add a build step which starts RDBMS docker containers before the third party tests are executed: Resolved
• Add .travis.yml: Resolved
• Execute Sqoop third party tests in the CI system: Open