(Atlassian) Software Development tools used in BE/CO Jira, Bamboo, Fisheye+Crucible, Clover

Outline Overview of our Atlassian tools Their use with a simple “change request” scenario How they integrate with each other 2

Atlassian Tools 3 Clover test coverage and code metrics Jira + Greenhopper issue tracking and planning Fisheye + Crucible code search and review Bamboo continuous integration and test

“Simple” software change lifecycle 1. Change request 2. Planning3. Assigned 4. Coding activities 5. Review 6. Integration and testing 7. Release 4

Jira Basic Entities Projects Components: sets of issues Issues: represents change Versions: set of issues to be completed together Workflows: Issue state, open, closed 5 CONCEPTs

Creating an Issue (Jira) 6 Required: Project Issue type Summary Priority Required: Project Issue type Summary Priority Optional: Components Versions Assignee Environment Description Time estimate Optional: Components Versions Assignee Environment Description Time estimate

Release Planning 7 Easy drag’n’drop Issue Ranking Easy drag’n’drop Issue Ranking Move issues to other versions Move issues to other versions

Assignment 8 Teams (individual or groups) associated with projects: –3 main roles: Administrators, Developers, Users Integrated with CERN user management –uses Atlassian Crowd (After assignment, developer starts coding activities) Start typing, search results appear automatically

Programming (Eclipse integration) Eclipse - Atlassian Connector links tools to IDE 9

Repository Exploring (Fisheye) 10 Code, file, and commit history search View repository activity and statistics

Repository Exploring (Fisheye) 11 Create a review for a set of files

Developer stats: hlieberm, supercoder. 12 Up FOR REVIEW?

Reviewing Code (Crucible) 13

Reviewing Code (Crucible) 14

Continuous Integration – Bamboo Entities Projects logical containers Build Plans: “recipe” for a project build and test Agents: executes a plan when queued Build trigger: when to queue a build plan for execution Build results: data associated with an executed build plan 15 CONCEPTs

Continuous Integration and Test (Bamboo) 16 Dependent builds

Continuous Integration and Test (Bamboo) 17 Build and test (all) success over time

Continuous Integration and Test (Bamboo) 18 Single test history across builds over time

Continuous Integration and Test (Bamboo) 19 Test coverage for project Code metrics Classes with highest risk

Preparing a project release (Versions) 20 Progress as issues closed

Jira and other tools integrated 21 Associated code changes are linked

Summary Good tools for development workflow Well integrated across suite and with Eclipse Many more useful features not mentioned here! 22

Other Jira Features For the Project: –Show portlets and project info –Activity streams –Graphs –Integration between the tools For the Developer: –Dashboard Plugins, pluggable, source code, integratable, –RFC, handler ACCOR workflow AND MUCH MUCH MORE 23

Creating an Issue (Jira – Agile) 24

Priorities and Versions Priorities: –Issue Priority: for user “impact” –Issue Ranking: for project ordering Versions: – A set of issues that are to be released together –Jira creates release notes from issue list 25 CONCEPTs

Testing (Clover) For assisting development of unit and function tests Shows: % of code covered by Tests the high risk classes Provides metrics: eg. cyclometric complexity 26

Preparing a project release (Versions) 27