Migration from Savannah to JIRA Alina Grigoras A. [email protected].

13
Migration from Savannah to JIRA Alina Grigoras A. [email protected]

Transcript of Migration from Savannah to JIRA Alina Grigoras A. [email protected].

Page 1: Migration from Savannah to JIRA Alina Grigoras A. Alina.Grigoras@cern.ch.

Migration from Savannah to JIRA

Alina GrigorasA. [email protected]

Page 2: Migration from Savannah to JIRA Alina Grigoras A. Alina.Grigoras@cern.ch.

ALICE Offline Week 2

AliRoot and Savannah

19/03/2014

8 years of full activity

5348 tracked issues in totalUntil now it fulfilled the needs of ALICE Offline

Page 3: Migration from Savannah to JIRA Alina Grigoras A. Alina.Grigoras@cern.ch.

ALICE Offline Week 3

Why JIRA Further development and support for GNU Savannah tool has stopped End of 2013 will mark the complete shut down of CERN Savannah instance

indefinite All projects that were not marked to be migrated will be lost! All migrated project will be still accessible using the old Savannah links, no

documented reference to Savannah tickets will be lost Following up an extensive evaluation CERN IT department chose JIRA as

tracking and planning tool Features:

Record tasks, requests and bugs Track their progress Organize, assign and prioritize Search, filter and report Developed on a plugin structure, a large plugin market already exists Offers an API to develop your own plugins Offers a REST API that allows the issues to be controlled from outside applications Synchronized with CERN Central Service for authentication and authorization

19/03/2014

Page 4: Migration from Savannah to JIRA Alina Grigoras A. Alina.Grigoras@cern.ch.

ALICE Offline Week 4

ALICE and JIRA

CERN JIRA service is handled by IT-PES-IS – Infrastructure Service – Alvaro and Borja

It offers 2 options: Central CERN instance – almost no customization Personalized instance

SSO/E-groups, Backup and Fail-over, Database, Server, Maintenance, Support, Updates

needs license for JIRA itself and all plugins Based on the decision of O2 CWG2 ALICE chose to have their own

private instance hosted on CERN infrastructure https://alice.its.cern.ch Instance that was already used by DAQ, now also by O2 and

Physics groups Synchronized with CERN authentication and egroups

19/03/2014

Page 5: Migration from Savannah to JIRA Alina Grigoras A. Alina.Grigoras@cern.ch.

ALICE Offline Week 5

JIRA – Basic concepts

19/03/2014

14.11.13B. von Haller tutorial

Projects

Components (sub-section)

Versions (milestones)

Issues

Level 1

Level 2

Project Categories

Issue TypesLevel 3

Sub-Tasks

Issue Types

Sub-Tasks

Sub-Tasks

Sub-TasksLevel 4

5/XX

Page 6: Migration from Savannah to JIRA Alina Grigoras A. Alina.Grigoras@cern.ch.

ALICE Offline Week 6

JIRA – Basic concepts

19/03/2014

Project : AliRootComponents : Simulation, Reconstruction, Analysis, …

Versions : vAN-today,

Issues

Level 1

Level 2

Project Categories : Offline

Issue Type : Production request

Level 3

Sub-Tasks

Issue Type : Porting request

Sub-Tasks

Sub-Tasks

Sub-TasksLevel 4

Issue Type : Bug

14.11.13B. von Haller tutorial

Page 7: Migration from Savannah to JIRA Alina Grigoras A. Alina.Grigoras@cern.ch.

ALICE Offline Week 7

JIRA - Workflows

19/03/2014

Default JIRA workflowAn workflow is defined by

• States• Transitions

Page 8: Migration from Savannah to JIRA Alina Grigoras A. Alina.Grigoras@cern.ch.

ALICE Offline Week 8

JIRA - Workflows

19/03/2014

Production request workflow

Page 9: Migration from Savannah to JIRA Alina Grigoras A. Alina.Grigoras@cern.ch.

ALICE Offline Week 9

JIRA – Browsing issues The default listing is not very friendly 2 options that can be combined

Filters – saved searches Dashboard – can contain widgets, including

filters Filters and dashboards can be shared between

users Reports :

Show statistics for particular people, projects, versions, or other fields within issues, based or not on a filter

Predefined reports available, extendable19/03/2014

Page 10: Migration from Savannah to JIRA Alina Grigoras A. Alina.Grigoras@cern.ch.

ALICE Offline Week 10

JIRA - Notifications Very flexible notification schema Notifications for

Reporter, assignee, watchers Enable/disable notifications per operation

Send email when somebody comments on an issue, but do no send email when the status of the issue is changing

Per component – assign a list of users that receive emails about all the issues related to a component

19/03/2014

Page 11: Migration from Savannah to JIRA Alina Grigoras A. Alina.Grigoras@cern.ch.

ALICE Offline Week 11

AliRoot and JIRA Migrated from Savannah to JIRA on 12/03/2014, trying to map

the original structure Due to increase of the traffic the service was moved this

morning to a new machine Access controlled thorough alice-off and alice-members

egroups After migration a new structure will be adopted profiting from

the JIRA flexibility, with 5 types of issues and their corresponding workflow:

Production request Porting request Development - Agile plugin Bug Support

The schema can evolve through time19/03/2014

Page 12: Migration from Savannah to JIRA Alina Grigoras A. Alina.Grigoras@cern.ch.

ALICE Offline Week 12

JIRA, Git and other goodies

JIRA offers a Git Integration Plugin Links git commits to JIRA issues In place at the end of this week

JIRA Agile plugin Enables agile development for JIRA

REST API – MonAlisa will automatically update the states of the productions requests

Plenty of other useful plugins

19/03/2014

Page 13: Migration from Savannah to JIRA Alina Grigoras A. Alina.Grigoras@cern.ch.

ALICE Offline Week 13

ALICE JIRA support Service Managers for the JIRA instance

Gabor Kiss <[email protected]> Sonia Rajput <[email protected]>

Main administrators of JIRA Contact them for questions and requests

E.g. project transfer or creation or customisation

JIRA administration project https://alice.its.cern.ch/jira/browse/JADMIN

19/03/2014