SOCCI Training. SOCCI: Science Operations Configuration Control Infrastructure. Vicente Navarro Fernando Perez Kaarel Hanson Kaarel Lumi

Transcription

1 SOCCI: Science Operations Configuration Control Infrastructure SOCCI Training Vicente Navarro Fernando Perez Kaarel Hanson Kaarel Lumi 18&19 January 2018

2 SOCCI ADVANCED

3 Topics and Schedule 1. Requirement Management - 45min 2. Test Management - 30min 3. Continuous Integration - 60min 4. Future Features - 45min

4 Requirement Management 1. Types and hiereachy of requirements 2. Workflow 3. Traceability 4. Importing Requirements

5 Requirement Management Hierarchy There are 4 types of requirement projects designed for SOCCI User Requirements URQ Mission Requirements MRQ System Requirements SRQ Software Requirements SWRQ In the requirement projects, we have identified 2 types of issues Requirement Design Component (only in SWRQ) User Requirement Mission Requirement System Requirement Derives Software Requirement Implements Design Component

6 Requirement Management Workflow Multi-stage WF Fully tailored for ESAC, based on best practices

7 Requirement Management Traceability Requirements can be traced from and to Requirements in different projects Design Components Documentation

8 Requirement Management Excercise Open SOCCI JIRA and Create in the Sandbox projects User Requirement Software Requirement Add Traceability User Requirement derives Software Requirement Design Component implements Software Requirement Open SOCCI Confluence and locate Sandbox Space Create an SRS following the convention ESAC-SANDBOX-SRS-<YourName> Add macros for software and user requirements in the SRS

9 Requirement Management Import Requirements Guide is provided in SUM-0001 Requirements can be imported in bulk from CSV Format of the CSV is provided in SUM-0001 Import file must be submitted to SITU

10 Test Management 1. Issue Types and Hierarchy 2. Cloning 3. Importing

11 Test Management Issue types and Hierarchy Test Management was originally designed for SOCCI engineering, hence, it is lightweight and rather simplistic We have designed a 3-level test management structure Test Case Test Design Test Specification Including an additional issue type for test results Test Record Test Specification Test Design Test Design TestCase TestCase Test Record TestCase TestCase Test Record TestCase TestCase Clone Test Record Test Record Test Record

12 Test Management Cloning Cloning works on every level of Test Management Cloning is used to create a set of test records for a campaing in a given Version (Tested In Release) Environment Test Campaign Execution (Labels)

13 Test Management Recap

14 Test Management Import Tests Guide is provided in SUM-0001 Test Cases, Designs and Specs can be imported in bulk from CSV Format of the CSV is provided in SUM-0001 Import file must be submitted to SITU

15 CONTINUOUS INTEGRATION

16 SOCCI Documentation SUM-0003 = Continuous integration isplay/soccibl/esa-socci-sum Baseline 1. Open SOCCI Confluence 2. Open SOCCI Baseline space 3. Open ESA-SOCCI-SUM-0003

17 Topics 1.Integrations / overall view 2.JIRA 3.Bitbucket 4.Jenkins 5.SonarQube 6.Nexus 7.DEMO

18 Tools

19 JIRA Integration with Bitbucket provides some useful links in JIRA issue view: 1. Branches 2. Commits 3. Pull requests 4. Create branch

20 Bitbucket Git repository Enterprise grade permission management - levels: projects, repositories, branches Pull requests between branches Code review based on pull requests

21 SOCCI Branching Model

22 Jenkins Best practice: 1+ build server per team, managed by team (Source: radar/techniques ) Build jobs

23 Jenkins We have a guide in SUM-0003 for setting up a Jenkins job that does the following, your requirements and experiences may vary: 1. watches all branches 2. builds when changes are pushed to Bitbucket 3. runs unit tests 4. runs SonarQube 5. deploys artifacts to Nexus 6. sends s 7. notifies JIRA 8. notifies Bitbucket

24 SonarQube Static code analysis Detects most common quality problems in several programming languages C/C++, JavaScript, C#, Java, COBOL, TypeScript, PL/SQL, PL/I, PHP, ABAP, T-SQL, VB.NET, VB6, Python, RPG, Flex, Objective-C, Swift, Web, XML Get trivial problems out of the way for code review and focus on important things

25 Nexus Repository for build artifacts for example.jar files Store each build for testing purposes Unique release builds and multiple snapshot builds

26 Tools One more time to tie it all together

27 DEMO 1.New feature branch 2.Make changes 3.New release branch 4.Pull request 5.Code review 6.SonarQube 7.Jenkins 8.Nexus

28 DEMO Screenshots

29 DEMO Screenshots

30 DEMO Screenshots

31 DEMO Screenshots

32 DEMO Screenshots

33 DEMO Screenshots

34 DEMO Screenshots

35 DEMO Screenshots

36 DEMO Screenshots

37 DEMO Screenshots

38 DEMO Screenshots

39 DEMO Screenshots

40 Continuous integration Questions? Thank you!

41 Conclusion All guides are given in the User Manuals! For additional support, please submit an request to SITU! Or get in contact with Vicente, Fernando, or the SOCCI Team Please let us know of your impression of the SOCCI Foundation Training Session Thank You!