Conventional Development. Manual Build process. Release Manager Testing Team. Developer Branch. Execute Manual /Automation tests.

Transcription

1

2 History Pioneer offers SAAS to Fortune 500 specialized in web marketing On/offshore engineering team working on a project for six years The project has evolved a lot in terms of size and functionality in the last six years We follow agile so our delivery time frame is usually around four weeks

3 Code Check-in Conventional Development Release Manager Testing Team Developer Branch Manual Build process Developer Branch Code Check-in Team Foundation server Deploy UAT/Staging environment Execute Manual /Automation tests Developer Branch Send feedback to the team

4 What was our problem? Offshore development adds complexity to our processes We have a limited release time to go to live on production In reality we cannot produce more than a build per day. The release process is too manual QA can easily get stuck due to some major issues of yesterday s build Feedback system is too slow for our development model and causes delays and costs too much

5 Solution Need a fast feedback system that responds on the same day/hour of change Automated Should have Alerts Integrated Reduce duration/costs

6 Continuous Integration (CI) Paul Duvall (Author of Continuous Integration: Improving Software Quality and Reducing Risk): Improving Software Quality and Reducing Risk, best practices of CI include: Committing code frequently. Categorizing developer tests. Using a dedicated integration build machine. Using continuous feedback mechanisms. Staging builds.

7 Who s Who The Roles Kidra- The Idealist Suren- The Commander Vara- The Professional Siva- The Finisher

8 CI Best Practices Automate the build Make the build self-testing Everyone commits to the baseline every day Every commit (to baseline) should be built Everyone can see the results of the latest build Automate deployment

9 Step 1: Environment Step 2: Artifacts Step 3: Configuration Step 4: Triggers Step 5: General Step 6: History

10 Checks the status (Ready.txt) Execute Test Cases Send Notification Log details Compile Run unit test cases if configured On success, Copies Build to server Copy Files to target servers On success, Triggers Selenium automation on target server Automated Integration and Deployment Development Machines Check-ins Code Check-in triggers Continuous Integration Pass Yes Success Build triggers Continuous Deployment Continuous Integration No Continuous Deployment Notification from VSTS-online Notification from VSTS online No Pass Yes Selenium Test case Execution Automated Test and Notifications

11 Continuous Deployment Workflow Automation Development Team VSTS VSTS-Online Continuous Integration Continuous Deployment On-Premise Deployment Automation Testing Release Configuration with VSTSonline Code/Edits files then commit changes Source Repo Commit to branch Trigger CI server(build Definition) NO Build Succeed? YES Trigger VSTS-Online server(release Definition) Notification NO Release Succeed? YES Trigger Selenium Automation Test cases NO Tests Succeed? YES Release

12 Process flow Diagram Delivery team Repository Version Control(VSTS-Online) Continuous Integration Continuous Deployment Staging servers Automation Testing Release Check-in Trigger Notification Check-in Trigger Notification Trigger Check-in Trigger Trigger Trigger Approval Notification Success Fail

13 Automation Testing Principles Scalability Accessibility Reusability Flexibility Quality Maintainability Results Communication Code Changes Audit/History

14 Automation Control Panel

15 Environment

16 Automation Datafeed

17 Automation Results

18

19 What are Continuous Integration (CI) and Continuous Deployment (CD)?

20 CI Definition Step 1 Step 2 Step 3 Step 4 Step 5 Step 6

21 CD Definition Step 1 Step 2 Step 3 Step 4 Step 5 Step 6

22 Configuration Dev machine Configure XAML Build Definition using visual studio Enable Continuous Integration VSTS Online Configure Release Definition. Map Build Definition to Release Definition(Artifacts). Enable Continuous Deployment. QA/Staging Configure selenium Test cases to run on server. Automate on deployed Builds

23 Continuous Integration[CI] :: Step 1 - General

24 Continuous Integration[CI] :: Step 2 - Trigger

25 Continuous Integration[CI] :: Step 3 Source Settings

26 Continuous Integration[CI] :: Step 4 Build Definitions drop

27 Continuous Integration[CI] :: Step 5 - Process

28 Continuous Integration[CI] :: Step 6 Retention Policy

29

30 Continuous Delivery [CD] :: Create Release Definition - Choose Empty Template

31 Continuous Delivery [CD] :: Step 1 - Environments

32 Continuous Delivery [CD] :: Step 2 - Artifacts

33 Continuous Delivery [CD] :: Step 3 - Configuration

34 Continuous Delivery [CD] :: Step 4 - Triggers

35 Continuous Delivery [CD] :: Step 5 - General

36 Continuous Delivery [CD] :: Step 6 History of Releases

37 Triggering the Continuous Integration

38 Queued Build on VSTS online

39 Completed Build on VSTS online

40 Completed Release on VSTS online

41 Notification from VSTS online

42 Constraints faced during Continuous Integration and Continuous Deployment: Constraint

43 Difference between XAML Build Definition and Task based definition: XAML Old feature for creating builds. VSTS online has provided compatibility for old XAML build definition to run in online. XAML templates can be created/updated using visual studio only. Recommended for small build running not more than 1hr. Recommended for existing xaml build definitions to use with new VSTS- online Task New Feature for creating build definitions Cannot be created using visual studio. Require VSTS online. Recommended for long running builds. Recommended for new projects. This is not recommended for new projects. Microsoft may deprecate this feature in future releases.

44 Default Templates is not loading

45 Default Templates is not loading

46 Continuous Deployment: Triggering selenium scripts Step 1:Environment Second file copy is workaround for triggering selenium automation script on the remote server. We can use shell script task to run shell commands on the remote server, if services required to run shell are enabled on remote.

47 Task scheduler is configured

48 Observations:

49 Pros and Cons in above process Pros: XAML build can be easily configured and Queue the build through Visual studio. We can reduce the time for Build Manager for initial level of Build and Deployment operations We can reduce the time for QA team for quick and sanity testing activities for each build. Dev team not required to wait for their fixes on build server immediately after their check-ins. Integration testing will be done and the results will be notified immediate after check-ins. Overall, we can save major time at each level of responsibility and that can be used in other areas of SDLC. Load testing can be done with free limited minutes.

50 Pros and Cons in above process Cons Unit testing is not included as a part of build and deploy process. Approval process for the fixes are not part of deployment.[code review is missing]. VSTS-Online has provided limited free resources.[free Build minutes] Build minutes will be charged after elapsed free minutes. Cost will be increased with increase in project size. We can use multiple agents to run concurrent build. VSTS charges for each individual agents. Required to create additional environment for sanity test to run selenium test.

51

52