2016 Federal User Group Conference - TeamForge Capabilities and Directions

1 Copyright ©2016 CollabNet, Inc. All Rights Reserved.ENTERPRISE CLOUD DEVELOPMENT

Scott RoseSr. Director of Product Management

@scottdrose

[email protected]

Capabilities and Directions

The Platform for Innovation, Collaboration and Agility

2 Copyright ©2016 CollabNet, Inc. All Rights Reserved.

Some of the products and features described hereinremain in varying stages of development and

will be offered on a when-and-if-available basis.

This roadmap is subject to change at the sole discretionof CollabNet, and CollabNet will have no liability for delay

in the delivery or failure to deliver any of the productsor features set forth in this document.

Information in this presentation is CollabNet Confidential


TeamForge CY16 Release Plan

TeamForge

8.2

TeamForge

16.3

TeamForge

16.7

Q1 Q2 Q3

CTF 8.2• Agile (PFs, Boards)• Association Viewer• SCM• UX – Top Nav v1• CRUS/CRIs

Q4

TeamForge

16.10

CTF 16.3• Insights (Beta)• Pull Requests• Cust

Enhancements/CRIs• Orch/EventQ• UX – Top Nav v2

CTF 16.7• DevOps• Version Control• Insights v2/v3• EventQ – TestLink• CRUS/CRIs

Feb

8th

Mar

31s

t

July


Proposed Licensing (16.7) with new TF Components

Forge IQ (Insights)

Trackers

CollaborationALM

SCM

Licenseexisting Tools

VersionControl

Licensenew

SVN, Git

Binaries

Code Review

B&T, FRS

Trackers (with Agile Boards)

Docs, Wikis, Discussions,

ActivityStreams

DevOpsPackage Object

FRS

Mobile

DevOps


TeamForge Primary Pillars

Agile Development

@Scale

EnterpriseInfrastructureRequirements

Context&

Traceability

Enabling Enterprise Agile Software and Project Engineering @ Scale


(Software) Development LifeCycle Traceability and Visibility

Scrum Team 2

Test (T) QA (Q)

ScrumTeam 1

Dev (D)

T Q Prod

Prod (P)

B

Sprint

Build?

Build?

Unit tests

Unit tests

Unit tests

Build?

Continuous Integration

Continuous Testing

Automated Tests

Automated Tests

Unit tests

Continuous Deployment Continuous Monitoring

Cont

inuo

us P

lann

ing

Continuous Improvement

Build (B)

Daily Daily Daily

Context&

Traceability


Yesterday’s traceability: the monolithic tool suite

Monolithic Tool Suite

Artifact C

Artifact D

Artifact E

Artifact A

Artifact B

• In decades past, traceability in software development has been limited to monolithic tool suites

Context&

Traceability


Tool A

Tool B

Tool C Tool D

Tool E

But “point” tools impedes traceability

Commit

Review

Req/Issue

Build

Deploy ??

Dilemma: traceability or best-of-breed point tools

As Engineering VP, I want to employ the best tools for the job, but I cannot sacrifice traceability

Context&

Traceability


...

Tool B

Tool D

Tool F Tool GTool E

Tool CTool A

CollabNet EventQ resolves this dilemma, without sync

•EventQ is an event-based metadata store, collecting data from all of your tools, across vendors

•Detects and infers associations between disparate tools

•Automation: Minimizes reliance on manual input

RS

C

S

B

B B

C C

B B

B

B

B

B

B

EventQ Eco-system

Context&

Traceability


Chained Associations = Traceability

A B C D

E

F

G

Context&

Traceability


Associations directly in context of tools Context&

Traceability


Associations

•Visual overview provides a summary of direct associations

•Includes third-party, integrated tools

Git Push Review Artifact Builds

Commit

Context&

Traceability


Traceability in Action – Time Context

Chain of associations on chronology details “traceability”

Ability to explore deeper levels of associations for full “root cause analysis”

Context&

Traceability


Roadmap: Event Traceability Extends to (Project) Activity Streams

Project activity streams keep team members informed of latest activities and comments

Surfaces relevant context and calls to action

Enhances social interactions, improving stickiness

Context&

Traceability


•Git (version control)

•Subversion (version control)

•Gerrit (review)

•ReviewBoard (review)

•Atlassian Crucible (review)

•Jenkins (build/CI)

•TeamCity (build/CI)

•Nexus (binary)

•Atlassian JIRA (issue tracking)

•Chef (Deploy)

OOTB Integrations Available Today Context&

Traceability


• Overarching Project Hierarchy– ALM Tools are components of a projects (not vice versa)– Complete flexibility (project level) to work across a variety of Open Source

tool chains (including 3rd party)– X-Project Visibility and Reporting– Hierarchical and Granular RBAC (Site, project and sub-project, file and branch)– Multiple work structures (task, team, release)

• Enterprise grade capabilities– On-premise and hosted – Distributed environments – Supports highly iterative and traditional enterprise release cycles– Scale and performance – marque enterprise customers, some with

environments containing > 1B+ commits

TeamForge Product Structure EnterpriseInfrastructureRequirements


CustomerData Center

Public Cloud Services (AWS)

CollabNet HostedCloud

Hybrid Cloud

Multiple Deployment Options

Roadmap

FedRamp Certification

Targeting July ‘16 in AWS Gov Cloud



TeamForge Authentication Features

•TeamForge is an off the shelf application server platform from CollabNet with several user interface access points: Web, Desktop, IDE, server tools and a number of third party integrations.

Web UICan use Web SSO orUsername/Password

Thick ClientsCan use Username/Password

TeamForge Application Server

JSP Pages

SOAP/Web services

API

Inte

rnal

AP

I

JBoss Services

- JAAS

• Active Directory• LDAP• Kerberos un/pw• Web SSO Key• Custom module

AuthenticationServices



Fine-Grained Role Based Access Control EnterpriseInfrastructureRequirements


One platform, one user interface, multiple technologies covered

• Both Subversion and Git supported as first-class citizens– Unified user experience, abstraction on commit level– We let their strengths shine through

• Key TeamForge features covering both SVN and Git– Security, standards and audit compliance

• Powerful Role Based Access Control (RBAC)• Traceability: who, what & when• Associations between commits and artifacts

– Enterprise grade scalability & replication management– Source code browsing and diffing– Code search across multiple repositories– Reporting

TeamForge SCM EnterpriseInfrastructureRequirements


Traceability: SVN & Git changes linked to same requirement

Git

Subversion

When & by whom What was done



• CollabNet has put alot of effort to find best possible Git-Gerrit settings and server hardware configurations for our customers

• Some of our customers have– More than 5 million Git fetch requests daily– More than 10 Gerrit master servers– More than 40 different “geographies” and replication servers– More than 100,000 active developers– More than 10 TB of source code– More than 20,000 repositories– More than 1000 CI servers

TeamForge SCM at Scale EnterpriseInfrastructureRequirements


Increase developer productivity by allowing both pull request- and individual commit-based reviews to be mixed and matched

• Use commit-based reviews for sensitive branches and bug fixes• Utilize merge-based reviews for scenarios like branch integration in feature-branch

development• Govern the choice of review models and specific workflows with rules and gating policies

TeamForge now supports Pull Requests

Unp

rote

cted

Br

anch

esPr

otec

ted

Bran

ches

master

release-3.0

GUI-integration

feature-23

COMMIT-BASED REVIEWS

PULL REQUEST

Agile Dev@

Scale


Both models have their individual merits and drawbacks

Depending on the scenario, either model may be better suited

No review model is best

Commit-based Review

Pull-request Review

Clean Commit History ✓No file is left unreviewed ✓Avoids proliferation of branches ✓Easy collaboration on features ✓Reviews of integration branch merges ✓

Agile Dev@

Scale


Enterprise Class Report Library Agile Dev@

Scale


Mobile Insights – Soon to be available in BetaDevelopment EXCELLENCE SCORECARD -> DIG DEEPER -> GET NOTIFIED!

Agile Dev@

Scale


Roadmap: Project workspaces

A

Iteration:

Alertsartf7221 is assigned to you

build 87 Failed: 1000 pass, 1 fail

rev 124 No activity for 10 days

build 123 Failed: compile failure

deploy 18 Aborted after 23 sec

>> Activity Stream

Tracker Title Assigned Priority

artf196781 Query Language, phase 2 none 2-High

artf120412 REST API handles SSO scenarios bpetri 3-Med

artf134052 Disallow users without SSO cred… Kpete 3-Med

artf120413 Synchronize users with LDAP… bpetri 4-Low

CI ScoreboardWhen Commits CI/Builds Test Failures

Latest 1ge2fg by jsmith #90 : Successful 0

Today 2 6 2

This Week 13 38 6

This Iteration 20 63 12

Task board

Sprint 12/2 – 12/25 Team: Mavericks

Cummulative flow chart

plan 12456 Stories, 20 Tasks, 23 Defects

Persona based tools and content are surfaced in project home

Example: Agile Developer Persona

Agile Dev@

Scale


Roadmap: Project workspaces Agile Dev@

Scale


Roadmap: Project workspaces Agile Dev@

Scale


Releases & Iterations

FOLDER

RELEASEITERATION

Agile Dev@

Scale


• TeamForge 8.1 introduced a new Tracker Kanban Board view (in addition to the traditional List, Plan and Track views). – The Kanban Board allows a team to visually convey a work item’s progress

(via Kanban cards) as it flows through a system or process– Access the Kanban Board by clicking KANBAN in the tracker view toggle

Tracker Kanban Board Agile Dev@

Scale


• Set limits on the number of artifacts which may be in a given state at any time.

• Receive visual notification when those limits are breached.

Kanban Board – Value Stream Limits and Notifications

The background on the Not Started state column

header indicates that there are too many artifacts in this state on this board

The limits are displayed below the state header

Agile Dev@

Scale


• End-to-end traceability and automatic audit trails across multi-vendor tools used throughout the development lifecycle

• Effective, compliant, and repeatable processes

• Governed IP search, discovery, and reuse across teams– Controlled release of IP for export compliance

• Centralized, pervasive fine-grained RBAC

• Global reporting with real-time company-wide visibility

Summary - Compliance, Governance, and IP Security

Visibility, traceability, and IP security across tools, assets, processes, and teams


Q&A

35 Copyright © 2016 CollabNet, Inc. All Rights Reserved.

Continuous Lifecycle Integration Featuring End-to-End Traceability

ALERT MONITORING

HEALTH EVENT

WORK ITEM

SERVICE DESK

COMPLIANCE AUDIT

SECURITY CHECK

DEPLOYMENT

EPIC

STORY

TASK

COMMIT

CODE REVIEW

CI BUILD

BINARY

TEST

PLAN CODE BUILD TEST RELEASE DEPLOY OPERATE MONITORREVIEW

RELEASE PACKAGE

New Features


•Regardless of which access method a user connects to TeamForge with, each requires a username/password to identify the user.

•When using an integrated Web SSO system, the password is replaced with an integration key ( see next page ).

•When using a thick client or integration the tool connects to TeamForge via the SOAP/Web services API.

•Authentication Requests are passed to the JBoss/JAAS service to verify the un/pw with an external source ( AD/LDAP/etc ).

•New user accounts are also verified with the same external source by making a simple un/pw authentication request.

•By using an external authentication source all aspects of password management are assumed to be managed by that source ( ie. Expiration, password strength, etc ).

TeamForge Authentication – Details


•TeamForge treats Web SSO as a user convenience. It is NOT used as an authentication service.

•Web SSO works by creating a trust relationship between the customer SSO and an Apache based integration kit which uses a private trust key which is then passed to the SOAP API for authentication – the trust key is given as the password.

•When TeamForge is integrated with a Web SSO system, it is expected that it is integrated with the same backend authentication source as the Web SSO system so that usernames and passwords are consistent between Web UI clients and all other Thick clients that access TeamForge via the SOAP API.

TeamForge Authentication – Web SSO


TeamForge 2016 Feature Planning

Version Control

Git Merge and Pull RequestsEvent Associations - Git code review activitiesGerrit 2.11/2.12 supportImproved Code Search

Tracker Navigation and FilteringAgile and Hybrid Agile Project Templates

Agile

Platform Differentiation

WebHooks (Jira Cloud) Navigation Design ImprovementsEvent Association ViewerExpanded Report Libraries & Parameterization

Event Associations - Testing IntegrationEvent Association – Deploy integrationEvent Associations Streaming CTF Mobile Services - Insights

Git Merge and Pull Requests in Code BrowserExpose History Protection in Code BrowserWorkspaces/Templates/Version Control

Project WorkspacesAgile Boards

Cus

tom

er E

nhan

cem

ents

App

licat

ion

Infr

astr

uctu

re

Plat

form

Infr

astr

uctu

re