{"id":15501,"date":"2022-01-18T15:30:23","date_gmt":"2022-01-18T20:30:23","guid":{"rendered":"http:\/\/www.iri.com\/blog\/?p=15501"},"modified":"2022-01-18T15:30:23","modified_gmt":"2022-01-18T20:30:23","slug":"db-subsets-in-jenkins-pipeline","status":"publish","type":"post","link":"https:\/\/www.iri.com\/blog\/test-data\/db-subsets-in-jenkins-pipeline\/","title":{"rendered":"Testing with DB Subsets in a Jenkins CI\/CD Pipeline"},"content":{"rendered":"

This Jenkins entry is the fourth in a series of articles on the use of <\/span>IRI test data management<\/span><\/a> software \u2013 that masks, synthesizes, or subsets data \u2013 to feed safe, referentially correct test data for DevOps to CI\/CD environments. Prior articles showed examples of test data creation in IRI software and the use of that data in <\/span>GitLab<\/span><\/a>, <\/span>AWS CodePipeline<\/span><\/a>, and <\/span>Azure DevOps<\/span><\/a>.<\/span><\/p>\n

In this article I will explain how to host Jenkins in a Google Cloud Platform (GCP) Virtual Machine (VM), and run an IRI <\/span>database subsetting<\/span><\/a> job to feed that data into a Jenkins pipeline.\u00a0<\/span>Subsetting produces a smaller, but referentially-correct copy of a larger database schema.\u00a0<\/span><\/p>\n

Subsetting is useful in software or database testing scenarios that do not warrant the (size) resources or (privacy) risk of using a copy of a production instance. Subsetting also preserves the business logic required in application testing, and when coupled with data cleansing and masking, the subsets are also sanitized and safe for use.<\/span><\/p>\n

\"\"<\/p>\n

So how do continuous integration tools like Jenkins benefit users when coupled with test data generation tasks like subsetting? Imagine a scenario where you are regularly building and deploying your application code within a CI\/CD pipeline. If your application consumes data from a database as part of its regular process, that process will need to be included in testing during certain stages of the CI\/CD pipeline.\u00a0<\/span><\/p>\n

For example, if we need to run tests on a website build that displays users\u2019 recent purchases from an online store, we will inevitably need to include tests related to the website\u2019s ability to query and accurately retrieve data from a database. By integrating a subsetting and masking job into the CI\/CD pipeline, we can create a comprehensive process in which we build and deploy these realistic, protected subsets alongside our application code to provide meaningful test data for use in the testing stages of the application\u2019s CI\/CD pipeline.<\/span><\/p>\n

This article assumes a certain level of familiarity with Jenkins and the Eclipse IDE, as we will be using the Jenkins Editor in <\/span>IRI Workbench<\/span><\/a> \u2013 the IDE for IRI test data and DB operations, etc. In summary, this article will discuss:<\/span><\/p>\n