Part of the DLM Story: Automated database build and test with TeamCity
Download as PPTX, PDF2 likes1,089 views
The document discusses a workshop on continuous integration (CI) for database management, highlighting the importance of automated builds and tests. It outlines the steps to achieve database CI, including source control and verification processes, and introduces the SQLCI plugin for TeamCity to facilitate these tasks. The workshop aims to equip participants with the tools to automate database development and maintenance effectively.
Part of the DLM Story: Automated database build and test with TeamCity
- 1. #sqlinthecity Automated database build and test with TeamCity SITC Workshop Cambridge, UK
- 2. What is CI? #sqlinthecity • Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early.
- 3. What is database CI? • It’s the same! #sqlinthecity • Applying the same approach to the database as we do for the application
- 4. The road to database CI 1. Source control 2. Automated builds 3. Automated tests 4. Frequent check ins of small changes #sqlinthecity
- 5. The road to database CI 1. Source control 2. Automated builds 3. Automated tests 4. Frequent check ins of small changes #sqlinthecity
- 6. Advantages of Automated Builds • Early warning of broken code • Constant availability of a "current" build • Don’t continue developing on a broken foundation • Many more…. #sqlinthecity
- 7. Goals of today’s workshop 1. Link a source control repository to a build system 2. Use the SQLCI resources to implement build steps that: • Verify that your database code has built successfully • Verify an upgrade to an existing database • Run database unit tests 3. Trigger builds automatically on changes being checked in to source control 4. Introduce artifacts as the basis for future repeatable deployments #sqlinthecity
- 8. • Plugin for TeamCity • Part of the Red Gate SQL Automation Pack • Includes 3 build runners: • Build • Sync • Test #sqlinthecity SQLCI Plugin – What is it?
- 10. • Subversion(SVN) • SQL Server 2012 • SQL Source Control • TeamCity #sqlinthecity Current setup
- 11. Creating a project • Creating a new TeamCity Project • Adding a VCS Root #sqlinthecity
- 12. The Build Step… #sqlinthecity CREATE TABLE foo… Does creation script run? ? 1. Convert scripts folder into package 2. Generate the creation script 3. Validate creation script
- 13. The Build Step… #sqlinthecity
- 15. Triggering… #sqlinthecity • Check it works so far.
- 17. The Sync Step… #sqlinthecity 1. Apply package version to target database 2. Deployment validation (is the target the same as the package?) V1.1 V1.2 compare
- 18. The Sync Step… #sqlinthecity
- 19. The Sync Step… • Check it works so far. #sqlinthecity
- 20. Capturing an upgrade script… /scriptFile:“<FilePath>“ #sqlinthecity We can use %build.number% to grab the current build number.
- 22. Try it for yourself…. • SQLServerCentral #sqlinthecity
- 24. The road to database CI 1. Source control 2. Automated builds 3. Automated tests 4. Frequent check ins of small changes #sqlinthecity
- 25. The road to database CI 1. Source control 2. Automated builds 3. Automated tests 4. Frequent check ins of small changes #sqlinthecity
- 26. Advantages of Automated Tests • Early warning of broken code • Constant validation of existing functionality • Detect when new changes introduce errors • Feedback on the current state of the code • Many more…. #sqlinthecity
- 27. SQL Test – What is it? #sqlinthecity • Add-in for SQL Server Management Studio • Builds upon tSQLt framework • Adds a simple UI for creating, managing and running database unit tests. • All tests are written in T-SQL www.tsqlt.org
- 28. Add database to SQL Test #sqlinthecity
- 29. Add a test
- 30. Manually running the tests… • Check it works so far. #sqlinthecity
- 32. The Test Step… #sqlinthecity 1. Build empty test database from package 2. Populate a new database with test data (optional) 3. Run tSQLt unit tests (report in JUnit format)
- 33. The Test Step… • Practical – sqlCI.exe Sync /package= <values5,2,3> /databaseServer=<value6> /databaseName=<value7> Optionally supply SQL Server Credentials #sqlinthecity
- 34. The Test Step… • Run the build #sqlinthecity
- 35. The Test Step… • Break the build #sqlinthecity
- 38. Try it for yourself…. • SQLServerCentral #sqlinthecity – How about a test to check the name added by the sproc?
- 39. Contact info • Tom Austin – Pre Sales Engineer at Red Gate – Email: [email protected] www.red-gate.com/ci #sqlinthecity