collabnet teamforge 6 · 2013-12-14 · why collabnet teamforge 6.1: engage the enterprise engage...

CollabNet TeamForge 6.1New Features and Enhancements

(between TeamForge 5.4 and 6.1)

2 Copyright © 2011 CollabNet, Inc. All Rights Reserved. CollabNet Confidential.

Why CollabNet TeamForge 6.1: Engage the Enterprise

Engage the Enterprise with CollabNet TeamForge 6.1

• Scale for the enterprise• High performance and throughput for code and file access• Automation for repetitive administration tasks

• Secure the development information• Simplified role based security, and role inheritance• Consistent tracker data quality, via input checks and workflows

• Simplify collaboration and improve visibility• Personalized experience, and simplified collaboration tasks• New reporting and metrics framework


Agenda

• Overview• Subversion Replication• Site Administration Features and Enhancements

• User Enhancements• Create User (Password Tickets and Organization Field)• Additional Email Addresses in User Profile• Multiple User Create

• System Tools• Site Broadcast Message• Audit Log

• Site-wide and Global Projects Roles• Project Groups

• Reporting and Analysis• Enterprise Reporting• Ad-Hoc Database Query


Agenda

• Project Administration Features• Project Hierarchies• Project Locking• Project Home Page Customization

• Discussion Improvements• HTML and RTF Supported for Discussion Posts• RSS Feeds• Reply Behavior• Expand/Collapse Forum Posts• Forum Monitoring and Posting

• Enterprise Tracking Improvements• Field to Field Dependencies• Field Layout Improvements• Field Input Value Masking

• Wiki Improvements• Source Code Improvements

• Anonymous Subversion Checkout


CollabNet TeamForge 6.1

CollabNet TeamForge (CTF) 6.1 is CollabNet’s converged ALM platform with all of the best features from CollabNet Enterprise Edition (CEE)

and CollabNet TeamForge available in a single product.

Note

This training course is specific to upgrades from CTF 5.4 to CTF 6.1

Copyright © 2011 CollabNet, Inc. All Rights Reserved. CollabNet Confidential.6

Subversion Replication

Motivation: Subversion Replication


• Problem• Checkout of code, binaries and large documents can be slow, in case of:

• Geographically distributed access.• Batch access (e.g. for CI activities).

• Traditional ways to tackle that problem are manual, expensive and risky:• Manual process; requiring special skills for setup and updates (e.g. security fixes).• Risk of inconsistencies: a) data inconsistency, b) user access / permission inconsistencies.• Reactive - no visibility across repository instances (e.g. utilization).

• Solution (top features)• Repository replication (with SVN Edge):

• Local access for resource intensive (read) access.• Based on established and proven SVN standards (svnsync, write-through proxy).

• Central management and monitoring:• Replication via deployment wizard, does not require special skills.• Automatic management of permissions, and ensuring of data consistencies.• Central monitoring of repositories (incl. available disk space, and network utilization).


• In CTF 6.1, you can specify Subversion replica servers for your site and make them available to your projects.

• Remote teams can perform read operations on local replicas while write operations are written back to the central server.



• A Subversion Edge server that is being managed by TeamForge can be put into Replica Mode.


Follow steps 1-4 to put the Subversion

Edge server into Replica Mode

Note

The permissions of the user who logs into Subversion Edge to create the replica determines the replica’s access to repositories in TeamForge


• Configuration in CTF for the Subversion Edge replica can be accessed by clicking the replica name under Admin -> Integrations -> SCM Integrations.


Click the replica name to edit

replica server properties


• Edit a repository within a project to see the available replica servers for the repository.


Select a repository and click edit to see

available replica servers

Replica servers hosting selected repository.

Available replica servers.


• At the project level under Source Code, users can see the master and replica repositories that have been set up in the project.


Note

It’s a good idea to use the description to help explain usage guidelines for available repositories in your project. Example “Brisbane Office Mirror”.

Master

Replica Checkout paths/commands for master repository and replica.


Site Administration Features:User + Role Management

Motivation: User + Role Management

• Problem• Need for delegation, simplification and bulk changes

• Allow multiple site admins to create users, without allowing them to view project details• Bulk change management (e.g. add users)

• Need for governance in user / role management• Ensure roles are managed consistently across projects• E.g. all developers can ‘change’ artifacts, but can ‘view only’ documents• E.g. for new ‘device F’ added to ‘handhelds’, automatically assign roles + users

• Solution (top features)• Simplified user management

• Bulk user creation; automation of standard processes (e.g. password initialization)• Site wide roles

• Fine-grained permissions for site administrators• Global project roles, and project groups

• Centrally manage (create, modify, delete) roles + users across all projects • Centrally manage (create, modify, delete) roles + users across groups of projects (e.g.

‘handhelds’)



Create User (Password Tickets and Organization Field)

• When creating a new single user account, you can now do the following:• Specify that an email be sent to the user with a link to set their password (do this

by leaving the password fields blank).• Include the users organization (via the new “Organization” field).

Leave the password fields

blank to send the user an email

allowing them to set their own password.

New Organizationfield.

Link to set password received via email.

Note

Password rules are set via site-options.conf.


Additional Email Addresses in User Profile

• Users can now include multiple email addresses in their user profile. These alternate email addresses can then be used as valid email addresses when posting to discussion forums, etc.

Alternate email addresses can be added by an administrator when editing a user’s profile or by a user via My Workspace-> My Settings.


Multiple User Create

• Multiple user accounts can now be created at once via: Admin -> Users ->Create -> Multiple Users.

The Multiple Users selection is available under the Createdropdown.

A space delimited list of users can be provided in the Users textbox.

List formatting instructions are included.

Note

Passwords can not be set when adding users via Multiple Users. These users will receive an email with a link to set their own password.


Motivation: Site-wide and Global Project Roles

• Problem – Simplify and Improve Permissions Management• Need to distribute discrete sets of site administration tasks between

different sets of users; i.e., User Administrators, System Administrators…• Apply a standard set of roles to all projects without re-creating and

maintaining the roles for each project; i.e., Product Developer, Project Manager…

• Solution – TeamForge 6.1 contains two new types of site-level roles

• Site-wide Roles: Allow you to create site administration roles with fine grained site-level administration and project permissions.

• Global Project Roles: Allow you to create project-level roles that are available to all projects within the TeamForge site.


Site-wide Roles

• Create Site-wide Roles via: Admin -> Roles -> Site-wide Roles.

If Prevents Access was checked during role creation, project permissions assigned to this role would not apply to

private projects.

Fine grained site administration permissions can

be set in the following areas.

Fine grained site project-level permissions can be set in the

following areas.


Global Project Roles

• Create Global Project Roles via: Admin -> Roles -> Global Project Roles.

If Prevents Inheritance was checked during role creation, project permissions assigned to this role would not apply to

private subprojects.

Fine grained site project-level permissions can be set in the

following areas.


TeamForge Role Overview

• With the addition of Site-wide and Global Project Roles, TeamForge now supports 4 different types of roles:

• Site-wide Roles: Roles with site-level administration and (optional) project permissions.

• Global Project Roles: Roles with project-level permissions made available to all projects on the site.

• Direct Roles: Roles with project-level permissions created within a specific project.

• Inherited Roles: Roles inherited into a sub-project from a parent project.


Motivation: Project Groups

• Problem – Simplify project permissions management for multiple sets of users across multiple projects

• Solution – Project Groups are a way to group associated projects and add users and roles to those projects quickly and easily.

• Users given a role in the project group will have that role in all of the projects included in the project group.

For example, users granted a Developer role in an Engineering project group will have that Developer role in all projects in the project group.

Note

A project group typically contains multiple projects.

A project can be assigned to multiple project groups.


Project Groups

• Project Groups are created via: Admin -> Project Groups -> Create Project Groups.

Click User Membership to add users to the project

group. Click Permissions to grant permissions to those

users.

Note

Roles granted to users via a project group are called derived roles (as opposed to direct roles). These projects are not listed under My Projectsbut are rather displayed under All Projects.

Click Add to add projectsto the project group.

• A Broadcast Message can be added to every screen in TeamForge via: Admin -> System Tools -> Broadcast Message.


Site Broadcast Message

Type in the broadcast message that you’d like displayed on every page and click Broadcast. Note that HTML tags are supported.

Once the message is entered, click Clear to remove the message.

The broadcast message you entered will be displayed at the top of every page within a yellow banner.


Reporting and Analysis

Motivation: Reporting + Analysis

• Problem• Need for visibility across projects and programs• Want standard reports but also flexibility (standard reports don’t always fulfill

needs)• Avoid tool proliferation – allow to work with preferred reporting tool

• Solution (top features)• Enterprise reporting

• New reporting and metrics infrastructure• Packaged dashboards and reports, based on best practices• Open to 3rd party tools

• Ad-hoc analysis• Flexible ad-hoc reporting, based on open standards (SQL)



Enterprise Reporting

• CTF 6.1 introduces the first phase of an enterprise reporting infrastructure.

• Metrics will be rolled out on a ad hoc basis, independent of the CTF release cycle.

• The new CTF external datamart is addressable via the CTF UI and via SQL by external applications.

Note

The datamart can be installed on the TeamForge server but the recommended configuration is to put it on a separate box.


Enterprise Reporting

• The first report that will be included in CTF is a Site Activity report accessible via: Admin -> Reports.

Chart View Grid ViewList of future reports

• The TeamForge database can be queried directly (read only) via: Admin -> System Tools -> Ad Hoc Database Query.


Ad Hoc Database Query

Note

Enter the SELECT query in the text box and click Run Query.

Its important to be cautious of the queries that are run via this method. Queries returning a large number of rows could impact site performance.

Query results


Ad Hoc Database Query – Examples

• What is the total number of projects:select count(*) from project;

• How many users are in an “Active” state:Select count(id) from sfuser where status=’Active’ and is_deleted=’f’;

• How many users have logged-in in the last x days:select count(id) from sfuser where last_login between '2011-04-01' and '2011-04-22';

• Show list of projects that have not yet been approved:select rnv.value from request_namedvalues as rnv, request where rnv.request_key_id=request.id and request.request_status='Pending' and request.request_type='SfMain.Project' and rnv.name='projectName';

• Artifacts with status “Open” in tracker1001• Select artifact.id, item.title from artifact, item, field_valuewhere artifact.id=item.id and field_value.id =artifact. status_fvand field_value.value_class=’Open’ and item.folder_id=’tracker1001’and item.is_deleted=’f’;

• Artifacts with status “Open” in project1003• Select artifact.id, item.title from artifact, item, field_value, folder where artifact.id=item.id and field_value.id =artifact. status_fv and field_value.value_class=’Open’ and item.folder_id=folder.id and folder.project_id=’proj1003’ and item.is_deleted=’f’;


Project Administration Features

Motivation: Project Administration

• Problem• Proliferation in number of projects leading to:

• Increasingly hard to maintain projects across project, and their relation to each other• Lack of sense of community, per project• Manual and error-prone tasks, when individually re-assigning users across projects

• Solution (top features)• Multi-level project hierarchies

• E.g. ‘device g’ as sub-project to “handhelds’ project• Optional inheritance of project role, while maintaining flexibility of roles by node

• Micro-sites, via project home page customization• Look-and-feel (and hyperlinks) unique to each project site• SVN-based, Web-publisher approach to customization



Project Hierarchies

• TeamForge 6.1 supports an n-level project hierarchy of projects/subprojects.

• Within a parent project, members with a role that has inheritance (i.e. contains permissions that cascade to subprojects) will have permissions within those subprojects.

Note

Changes to inherited roles in a parent project will cascade to subprojects.


Project Hierarchies

• A project hierarchy can be set after a project has been created via: Project Admin -> Project Settings -> Add Parent.

The Add Parent button displays a list of available projects to add as a parent.

Note

A project can only have a single parent. But, a parent project can have multiplesubprojects.

In CTF 6.1, inheritance is limited to roles. In future releases, other tools may be inherited to subprojects (e.g. Trackers).

The project path is displayed at the top of the project toolbar and can be hidden if desired

(click “Hide Project Path”).


Project Locking

• Projects can be put into a Locked state in CTF 6.1. • When a project is in a locked state, all project data is accessible but read-only.

• Projects can be locked via: Project Admin -> Project Settings -> Lock Project.

Note

Locking a parent project does not lock its subprojects.

Project administrators can unlock a project at any time.

Locked projects are indicated as such by the Locked icon in

the project title bar


Project Home Page Customization

• In CTF 6.1, you now have the option of creating fully customized project home pages.

• At Project Admin -> Project Settings, there are two project home options:• Show default project pages and components• Show custom web page (new)

Custom web page option

By default, CTF will strip HEAD content of custom

HTML pages. If you want that HEAD content preserved,

select Preserve HTML head content.

Note

At this time, project home option settings are not saved with project templates.


Project Home Page Customization

• To create a custom HTML home page, do the following:1. Check out the Subversion repository called “Publishing” using a Subversion client.2. Create ‘www’ as a top-level directory in the repository and in that directory create

an ‘index.html’ file with the custom HTML home page content.3. Check new files/directories back into the repository.

Subversion check out command/path.

Checkout ‘Publishing’ repository Create ‘www’ directory and ‘index.html’ file Check-in ‘www’ and ‘index.html’

1 2 3


Project Home Page – Example

Example custom home page.

Note

The ‘www’ directory under the Publishing repository is a Web space that can contain unlimited directories, HTML files, images, etc. Therefore, you can create a complex home page structure just as you would when building a Web site.


Discussion Improvements

Motivation: Discussions

• Problem• Increasingly users are active across a multitude of discussions groups

• Need to easily stay updated, within choice of user client• Numbers of users growing quickly per discussion group

• Need to restrict information traffic per discussion groups• Need to broaden community, while ensuring governance

• Solution (top features)• RSS feeds for discussion groups• Discussion group specific settings e.g. for reply behavior

• Reply behavior options (no replies, to sender only, ….)• Trusted users, who can overwrite behavior• Forum monitoring options, and positing by guests



RSS Available for Discussion Forums

• RSS feeds are now available from discussion forums by clicking on the discussion summary page.

Click the RSS icon to choose the application to use to subscribe to the feed.


Reply Behavior and Trusted Users

• You can now configure the Reply Behavior for each discussion forum. The options are:

• To sender only, To the list (default), To an alternate address, and Do not reply.

• Email from Trusted Users bypass moderation and are sent directly to the forum.

Reply behavior. To an alternate address

selected.

Trusted users whose forum posts will

bypass moderation.

Note

Additionally, Moderators can accept, deny or approve moderated messages from their email client.


Expand/Collapse Forum Posts

• You can now Expand/Collapse forum posts in the List of Posts view.• Individual posts can be expanded or collapsed.• Or, you can expand all or collapse all posts.

Expand All or Collapse All posts.

Collapse individual post.


Forum Monitoring and Posting Configuration Options

• New configuration options have been added to control who can monitorand post to discussion forums.

• Options can be controlled at 3 levels:• Site• Project• Forum

• Monitoring and Posting can be restricted to the following audiences:• Allow only forum admins• Users with role permissions• All logged in users• Allow site users and guests

Restrictions cascade downward

Note

Monitoring and posting configuration options are set via site-options.conf.


Forum Monitoring and Posting Configuration Options - Project

• Project-level monitoring and posting settings can be found at: Project Admin -> Discussion Settings.

All configuration options are available at the project-level in this case because no restrictions were set at the site-level.


Forum Monitoring and Posting Configuration Options - Forum

• Forum-level monitoring and posting settings can be found by editing the discussion forum.

Discussion forum level configuration options.

Available options are determined by site and project level restrictions (if any).


Forum Monitoring and Posting by Guests

Anonymous poster’s email addresses are displayed rather than the poster’s real name.

When allowed per discussion forum configuration, guests can monitor forums via a new tab in the monitoring popup.

Note

Monitoring via the UI can only be done by users with forum administration permissions.

Anonymous users can subscribe via “<mailing list name>-project name-subscribe@domain”.


HTML and RTF Supported for Discussion Posts

• Forum messages support HTML and RTF formatting.• HTML/RTF formatting is preserved in email received from discussion forums.• HTML/RTF formatting is included as an attachment to the post in the Web UI.

Email sent with formatting Email received (HTML formatting maintained)


HTML and RTF Supported for Discussion Posts

The body of forum messages within the Web UI remains text. However, if the original email contained formatted text, that formatted text is included as an attachment.

Forum message attachment

Discussion Post within the CTF Web UI


Enterprise Tracking Enhancements

Motivation: Enterprise Tracking

• Problem• High number of custom fields, and increasingly complex processes

• Custom fields poorly documented, used incorrectly or not at all• Risk of data inconsistencies, as field combinations grow

(e.g. ‘supported database’ applies to ‘application’, but not to ‘shell script’)

• Solution (top features)• Custom help, and validation rules, per tracker fields• Field-to-field dependency settings



Tracker – Field Help

• Help text can be added for any configurable or user defined field.

Field Help is indicated by a “?” icon before the tracker field.

Help Text can be specified when creating or editing a tracker field.


Tracker – Field to Field Dependencies

• In CTF 6.1, field to field dependencies have been introduced in the Tracker.

• Field to field dependencies allow you to control what shows up in a child dropdown list based on the value selected in a parent dropdown list.

• A deep hierarchy of dependent fields can be created.

Select Parent Field

Map child values to

parent values.


Tracker – Field to Field Dependencies

• In the example on the previous slide, we created the following field to field dependencies:

Instructor-led Training: PowerPoint DeckTraining BookletStoryboard

Web-based Training: PowerPoint DeckRecorded DemonstrationAudio RecordingStoryboard

Graphics: Icon/ButtonsDiagrams


Tracker – Field Layout Improvements

• The ability to customize the a tracker layout has been enhanced in CTF 6.1. There are now 3 types of content separators:

• Section Separator• Column Separator• Row Separator

Section

Column

Row

Example Tracker Layout

Section 1

Section 2

Section 3

Column

Row

Row

Section

2 Columns within a Section

3 Rows within a Column

2 Rows within a Column

1 Row within a Column


Tracker – Field Layout Improvements

Drag and drop separator to desired location

Resulting tracker layout

A label can be specified

when adding a

separator


Tracker – Field Input Value Masking

• You can now specify validation rules for Text Entry fields.

Check to enable Field Validation

Regular Expression to validate text entry

against

Test string and validation of test

Regular expression quick reference

A green checkmark will be displayed as soon as the entered text validates


Wiki Enhancements

Motivation: Wikis

• Problem• Need to radically simplify Wiki usage, as Wiki’s get adopted across enterprise

• Quickly add plugin-ins and widgets • Enable users to manage Wiki’s without special html skills

• Solution (top features)• WYSIWYG editor for Wikis• Plug-ins (using JSPWiki)



JSP Wiki Enhancements

• JSP Wiki has been upgraded to version 2.8.3.• New features include the following:

1. WYSIWYG editor2. Inserting variables: http://www.jspwiki.org/wiki/WikiVariables3. Tabbed sections: http://www.jspwiki.org/wiki/HowToCreateATabbedSection4. Collapsible lists: http://www.jspwiki.org/wiki/CollapsibleList5. Zebra tables: http://www.jspwiki.org/wiki/ZebraTableStyle6. Sortable tables: http://www.jspwiki.org/wiki/SortableTables7. Filterable tables: http://www.jspwiki.org/wiki/BrushedTemplateFilteredTables8. Wiki Plugins:

a) Counter: http://www.jspwiki.org/wiki/Counterb) Current Time: http://www.jspwiki.org/wiki/CurrentTimePluginc) Image Plugin: http://www.jspwiki.org/wiki/Imaged) Index Plugin: http://www.jspwiki.org/wiki/IndexPlugine) Insert Page: http://www.jspwiki.org/wiki/InsertPagef) Page View: http://www.jspwiki.org/wiki/PageViewPluging) Referred Pages: http://www.jspwiki.org/wiki/ReferredPagesPluginh) Referring Pages: http://www.jspwiki.org/wiki/ReferringPagesPlugini) Search: http://www.jspwiki.org/wiki/SearchPluginj) Table Of Contents: http://www.jspwiki.org/wiki/TableOfContentsPlugink) Wiki forms: http://www.jspwiki.org/wiki/WikiFormsPlugin

http://www.jspwiki.org/wiki/WikiVariables

http://www.jspwiki.org/wiki/HowToCreateATabbedSection

http://www.jspwiki.org/wiki/CollapsibleList

http://www.jspwiki.org/wiki/ZebraTableStyle

http://www.jspwiki.org/wiki/SortableTables

http://www.jspwiki.org/wiki/BrushedTemplateFilteredTables

http://www.jspwiki.org/wiki/Counter

http://www.jspwiki.org/wiki/CurrentTimePlugin

http://www.jspwiki.org/wiki/Image

http://www.jspwiki.org/wiki/IndexPlugin

http://www.jspwiki.org/wiki/InsertPage

http://www.jspwiki.org/wiki/PageViewPlugin

http://www.jspwiki.org/wiki/ReferredPagesPlugin

http://www.jspwiki.org/wiki/ReferringPagesPlugin

http://www.jspwiki.org/wiki/SearchPlugin

http://www.jspwiki.org/wiki/TableOfContentsPlugin

http://www.jspwiki.org/wiki/WikiFormsPlugin



Editing toolbar

Editor selector (Plain Editor selected)

Syntax reference

View as HTML or PDF



WYSIWYG editing menu

Editor selector (WYSIWYG Editor

selected)

Note

Word and Excel files can now be imported into a wiki page.

Also, the WYSIWYG editor can be turned off via site-options.conf.


Source Code Enhancements

Motivation: Anonymous Checkout

• Problem• Special requirements for open source projects

• Checkout allowed anonymous• However commit requires authentication

• Solution (top features)• Support for anonymous checkout



Anonymous Subversion Checkout

• To allow anonymous checkout from Subversion repositories, the project administrator must:

• Make the project public• Grant “Allow All Site Users and Guests” the “SCM View” permission


• When accessing a project as an anonymous guest, the “checkout commands”on the Source Code home page show the guest-specific command.

• Guest checkout occurs without any authentication (enter “guest” as the username and no password).

• Checkout string is: <domain>/svn/<repo url name>

Anonymous Subversion Checkout

Guest-specific checkout commands.

Note

Only anonymous checkout is allowed. Anonymous check-in for example is not.


Congratulations!You have completed the “What’s New in CollabNet TeamForge 6.1” training course.

For additional training, see: http://www.open.collab.net/training/ctf/.

LIMITED USE OF TRAINING MATERIALSUse of these CollabNet Training Materials is limited to the terms of your license agreement with CollabNet, Inc.For more information regarding your license to use these CollabNet Training Materials please contact CollabNet +1-650-228-2500.

http://www.open.collab.net/training/ctf/

collabnet teamforge 6 · 2013-12-14 · why collabnet teamforge 6.1: engage the enterprise engage...

Documents