Continuous Integration Ensemble / HealthShare Health Connect

Transcription

1 Continuous Integration Ensemble / HealthShare Health Connect

2 The scope of IT within an organisation is largely related to automating Business processes. So why not automate IT processes for once?

3 Version Control

4 Manual Version Control Worst case scenario: no periodical copies of the source code are made, which may cause issues on the Live environment to take a long time to be reverted as they require intervention of the Development team Usual scenario: each member of the Development and Operations teams is expected to take periodical copies of the source code and store them either locally or centrally It may be challenging to find the correct version of the code that should be used when reverting an issue, which could occur in any environment No auditability or change log mean high dependency on each team member

5 Automated Version Control Centralised, backed up Version Control System (e.g. Git or Subversion) stores any changes to the source code Branches for each environment and for each new feature or troubleshooting activity mean parallel streams of work can take place in a reliable manner Release Management Process may ensure the VCS is kept up-to-date by requiring the Operations team to only deploy code that is made available on the VCS Central history means lower dependency on each team member: Development team can scale up and down, suppliers can easily join or be dismissed, not all Operations team members need to know every technology in depth

6 Automated Version Control cont. Ensemble/Health Connect Repository environment-live environment-uat environment-base feature-1 master (DEV) feature-2 time

7 Testing

8 Manual Testing Developers/Testers spend time producing test scenarios or gathering them from Business resources Test scenarios are forgotten once new features go live New changes to the Live environment may cause unexpected issues (butterfly effect) Considerable effort is spent on troubleshooting and retesting activities in order to solve recurrent issues

9 Automated Testing Test scenarios are included as part of the code base during the implementation of every new feature Developers, Testers and Business resources time is optimised as they don t need to recreate test scenarios when an issue arises Butterfly effect is considerably reduced as the delivery of every new feature requires all tests to pass Every issue only happens once as test amendment prevents it from happening again Automated Integration Testing can be introduced via service virtualisation, i.e. mock-ups

10 Build and Deployment

11 Manual Build and Deployment Operations team members (or Developers!) manually gather the source code and dependencies necessary for every new deployment Building and deploying a new release requires knowledge of the system, making it difficult for multiple team members to be held responsible for it Mistakes can cause issues and potential downtime during or after the deployment

12 Automated Build & Deployment New system features are released in a consistent, automated manner Operations team members can safely build and deploy releases without knowledge of the system Mistakes due to manual tasks are significantly minimised

13 Continuous Integration

14 Concept Integration here refers to code integration a.k.a. code merge The longer is takes for new features to be released, the higher the risk that they will conflict with other features being developed Merging the source code as often as possible is the best approach for minimising code integration issues: Developers should commit changes frequently, so little time is spent merging their changes to the rest of the code Commits should be tested and deployed frequently, so issues can be identified early in the process

15 Concept cont. CI only adds a thin layer that orchestrates the process: 1. Identifying changes to the source code (Version Control) 2. Regress (and integration) testing them 3. Building and deploying CI creates a quality-oriented atmosphere Ensures VCS is updated by Developers Ensures tests are built and maintained over time Ensures multiple environments do reflect VCS

16 Continuous Delivery v Continuous Deployment

17 Demo

18 Demo Architecture notify code change run automated tests build release deploy update commit status

19 Release Management

20 Suggestion Phase 1 Integrella Set up GitLab and guide its use by Developers Produce a template Deployment Form and a Manual Fill in Deployment Form for deployment on UAT and LIVE Developers Keep GitLab up-to-date Fill in Deployment Form for deployment on UAT and LIVE Operations Responsible for deployments on UAT and LIVE with help

21 Suggestion Phase 2 Integrella Produce test automation framework and guide its use by Developers Produce automated test cases (requires input from the customer) Set up Jenkins so that tests run once a day on the DEV, BASE and UAT environments Developers Produce automated test cases

22 Suggestion Phase 3 Integrella Produce build and deployment scripts and guide their use by Operations Operations Builds and deploys releases via the scripts

23 Suggestion Phase 4 Integrella Set up Jenkins so that CI process is fully implemented Tests are run after each commit Build and Deployment are automated (except for Live environment)

24 Questions?