Dimensions CM 12.1 Sales and Support Workshop

Report
Serena Dimensions CM 12.1
Agenda
• Introduction : évolutions du marché de la GCL
• Principales nouveautés de Dimensions CM 12.1
• Thème principal : gestion des déploiements
• Toutes les autres nouveautés
• Questions
2
Evolution du marché de la GCL
Adoption des méthodes “Agiles”
Complexité des Releases
Reporting et visibilité Projet
3
L’adoption des méthodes Agiles continue de
progresser
4
Les motivations pour adaopter une méthode Agile
Pas simplement de
l’efficacité pour les
développeurs mais
des objectifs plus
stratégiques
5
La satisfaction vis à vis du processus de
déploiement est basse
6
Principales nouveauté de Dimensions CM 12.1
Nouvelles fonctions de déploiement
• “Deployment View” centralisée
• Automatisation des déploiments et retour-arrière
• Meilleur contrôle du processus
Améliorations du Client Web
• Nouvelle “Home page” configurable
• Supports des vues multi-rapports
• Affiche les historiques de builds et de déploiements
Amélioration de l’expérience utilisateur
• Amélioration de la gestion et de la fusion de Streams
• Support pour VS 2010 et Eclipse/Wind River Workbench
• Amélioration des performances et modèle de processus OOTB
7
Dimensions CM – Les processus GCL Couverts
Gestion du Changement
and
Processus GCL Globaux
Automation, Traceability, Enforcement
Process
Change Requests, Issue Tracking, Audit Control
Workflow
Control
Gestion de Configuration
Version Control, Stream Management, Baseline Management
Gestion de fabrication
Continuous Integration, Impact Analysis, Build Automation
Gestion des Déploiment (Release)
Packaging, Deployment, Acceptance testing
8
Roadmap and Platform Matrix
http://roadmap.serena.com/
9
Les nouvelles fonctions
de Déploiement
10
SERENA SOFTWARE INC.
Agenda
• Pourquoi améliorer les fonctions de déploiement
• Revue des nouvelles fonctionnalités
• Aperçu en “live”
11
SERENA SOFTWARE INC.
La satisfaction vis à vis du processus de
déploiement est basse
12
Comparaison des fonctionnalités
< 12.1
12.1
Deploy performs stage change for
requested item, request, or baseline.
New Promote and Demote commands
for changing stage of item, request or
baseline for improved control and
flexibility.
Deploy performs deploy or rollback
based on specified stage.
New Deploy and Rollback commands
for greater area control and flexibility.
Unable to rollback changes to area
without stage change.
Rollback command provided for
greater area control and flexibility.
Files automatically deployed with
stage change.
Automatic (default) file deployment is
optional and based on project/area
relationship so each area can be
different.
13
SERENA SOFTWARE INC.
Comparaison des fonctionnalités (suite)
< 12.1
12.1
Deployment operations are
synchronous in the client session.
Deployment operations are
asynchronous in the client session to
improve performance.
Deployment operations are
asynchronous with each other.
Deployment operations are
synchronous by area to improve area
integrity.
Builds can execute at the same time
as a deployment.
Builds execute synchronously with
deployment tasks to improve build
integrity.
Deployment area history and content
difficult to determine.
Deployment View in Web Client
designed with the
Deployment/Release Manager in mind.
Active-revision (highest revision at
stage is always in area)
Revision(s) in area are exactly what
the user requests.
14
SERENA SOFTWARE INC.
Revise An Item
Revise
Initial
Stage
foo.c;5
DEV1
DEV2
DEV3
•
•
Sets the item revisions Stage attribute to the Initial Stage
Does not Deploy the revision to any Areas (no Areas selected)
Revise An Item with Selected Areas
Revise
Initial
Stage
foo.c;5
DEV1
foo.c;5
DEV2
DEV3
•
•
•
foo.c;5
Sets the item revisions Stage attribute to the Initial Stage
Deploys the actual revision to any Areas selected at the Stage
Deploys according to the Area deploy sequence (if supplied)
Promote Item
Revise
foo.c;5
Initial
Stage
DEV1
Promote
foo.c;5
foo.c;5
DEV2
DEV3
ST
ST1
ST2
foo.c;5
ST3
ST4
•
•
Sets the item revisions Stage attribute to ST
Does not deploy any items (no Areas selected)
Promote Item With Area Selection
Revise
foo.c;5
Initial
Stage
DEV1
Promote
foo.c;5
foo.c;5
DEV2
DEV3
ST
ST1
foo.c;5
ST2
foo.c;5
ST3
foo.c;5
ST4
•
•
•
Sets the item revisions Stage attribute to ST
Deploys the actual revision to any Areas selected at the Stage
Deploys according to the Area deploy sequence (if supplied)
Promote Item Beyond The Next Stage
Revise
foo.c;5
Promote
Initial
Stage
foo.c;5
ST
foo.c;5
DEV1
REL
foo.c;5
ST1
REL1
foo.c;5
REL2
foo.c;5
foo.c;4
DEV2
ST2
DEV3
foo.c;5
REL3
ST3
foo.c;4
ST4
•
•
•
Sets the item revisions Stage attribute to REL
Deploys the actual revision to any Areas selected at the Stage
Deploys according to the Area deploy sequence (if supplied)
•
•
Promotes to ST and all other intermediate Stages
Does not Deploy to any Areas at intermediate Stages even if they are deploy by default
Deploy An Item Revision
Revise
foo.c;5
•
•
•
Initial
Stage
DEV1
foo.c;5
DEV2
foo.c;4
DEV3
foo.c;5
Only allowed if the Item Revision is at that Stage
Deploys the actual revision not the active revision at the Stage, will overwrite an
existing file
Does not affect any other Areas under the Stage
Deploy An Item Revision
Revise
foo.c;5
Initial
Stage
ST
DEV1
foo.c;5
ST1
DEV2
foo.c;4
ST2
DEV3
foo.c;5
ST3
ST4
•
Only allowed if the Item Revision is at that Stage
foo.c;5
Deploy An Item Revision
Revise
foo.c;5
Initial
Stage
Promote
foo.c;5
ST
DEV1
foo.c;5
ST1
foo.c;5
DEV2
foo.c;4
ST2
foo.c;5
DEV3
foo.c;5
ST3
foo.c;5
ST4
•
•
•
Only allowed if the Item Revision is at that Stage
Deploys the actual revision not the active revision at the Stage, will overwrite an
existing file
Does not affect any other Areas under the Stage
Deploy A Previous Item Revision
Revise
foo.c;5
Initial
Stage
Promote
foo.c;5
ST
DEV1
foo.c;5
ST1
foo.c;5
DEV2
foo.c;4
ST2
foo.c;5
foo.c;4
DEV3
foo.c;5
ST3
foo.c;5
ST4
•
•
•
Only allowed if the Item Revision is at that Stage
Deploys the actual revision not the active revision at the Stage, will overwrite an
existing file
Does not affect the other Areas under the Stage
Deploy A Previous Item Revision
Revise
foo.c;5
Initial
Stage
Promote
foo.c;5
ST
DEV1
foo.c;5
ST1
foo.c;5
DEV2
foo.c;4
ST2
foo.c;5
foo.c;4
DEV3
foo.c;5
ST3
foo.c;4
foo.c;5
ST4
•
Deploy can deploy to any areas under a Stage
Actioning Requests
New
Assigned
Dev
Complete
Stage: ST
Areas: ST1
ST1, ST2 & ST4
CR_1
Revise
foo.c;5
In ST
Initial
Stage
DEV1
Promote
DEV2
DEV3
foo.c;5
New Request
•
•
Assigned to developer
Developer revises Item
against Request
Developer Actions Request
•
foo.c;5
foo.c;5
•
ST
•
ST1
foo.c;5
ST2
foo.c;5
ST3
ST4
foo.c;5
•
•
QA Actions Request To “In ST”
State
User adds Areas ST2 & ST4 to
ST1 which is automatically
selected
Issues Promote To “ST” State
and Deploys to ST1, ST2 &
ST4
Séparation des Stages & Areas - Areas
• Rules
• To be in an Area an object has to be at that Areas Stage or higher
• User has to have authority on the area in the Project/Stream to use the Area
directly
• Deploy Item(s), Request(s) or Baseline(s)
• Distributes objects to one or more Area(s)
• Objects have to be at the Areas Stage or higher
• The item(s) will overwrite what is there already
• Rollback
• Removes objects from one or more Area(s)
• Previous item revisions will be distributed to the Area
• Rollback entire transaction (area version)
• Deploy & Rollback available via
• New Deployment View
• Promote or Demote
Séparation des Stages & Areas - Stages
• Rules
• User has to have authority on the Stage in the Project/Stream to use the Stage
directly
• Promote Item(s), Request(s) or Baseline(s)
• Changes Stage of object up the Stage Lifecycle
• Dialogue allows user to select area(s) for deployment
• Promote can cross multiple Stages, no deployment at intermediate Stages
• Demote Item(s), Request(s) or Baseline(s)
• Changes Stage of object down the Stage Lifecycle
• Dialogue allows user to select area(s) for deployment at the demoted to Stage
• Demote can cross multiple Stages, mandatory rollback of all Areas
• Demoted objects can not be left in any Areas
• Area Definition
• Deploy by default
• Deploy sequence
Others
• Deploy By Default
• Areas selected for deployment automatically
• May only be deselected if user has authority on the Area in that
Project/Stream
• Will be deployed to if the user has no area authority
• Area sequence number
• Any numbers will be deployed in sequence
• Default zero deployed last in parallel
• No Move on Deploy
• CM cannot understand area groups and path to production
• CLEAN command which object option
Mise à jour des versions antérieures
• Read the installation guide for the platform.
• Before the upgrade, perform an AUDIT to ensure integrity of deployment
areas. Remember: only controlled content is reported.
• After upgrade, you cannot deploy to an existing area until the manual
upgrade utility has been executed.
• The new audit trail will not contain all the history of previous deployments.
• The new audit trail will only consist of the initial area version which contains
all of the items currently deployed to the area.
• zOS areas require a 12.1 zOS agent in order for the migration to complete
successfully. Older zOS agents do not support the upgrade process.
• Rollback of item(s), request(s), baselines(s) deployed prior to the upgrade is
not supported. Use deployment of new revisions instead.
29
SERENA SOFTWARE INC.
Deployment View
• New tab in Web Client for managing deployment areas.
• Designed to be used by Deployment and Release Mgrs.
• Displays Pending items, requests, and baselines per stage or area.
• Displays Queued deployment related tasks per stage or area.
• Displays deployment related task history per stage or area.
• Allows execution of action, promote, demote, deploy, rollback, build, and
audit operations against selected artifacts.
30
SERENA SOFTWARE INC.
Nouvelles propriétés pour les projets
• Deployment model (manual and automatic) has been renamed to “Use local
stages”
• Automatic deployment (action driven promotion) is now “Use local stages” =
OFF.
• Manual deployment is now “Use local stages” = ON.
31
SERENA SOFTWARE INC.
Déploiement de “Régression”
• Regressions are allowed by default.
• To disable regression checks, set the following variable in dm.cfg:
DM_NO_DEPLOYMENT_REGRESSION
FALSE
• When regression checking is disabled, what you ask for is what you get.
• Be careful with default areas in this environment.
32
SERENA SOFTWARE INC.
Ordonnancement
• Scheduled deployment operations appear in the queue for an area until the
execution time is reached.
• Promote, demote, deploy, and rollback all support scheduling of area
operations.
• Scheduled builds will not display in area queue in this release.
33
SERENA SOFTWARE INC.
Build
• Deployment builds participate in area queue like other deployment jobs.
• Deployment and work area builds have the ability to “lock” the search path
from changes while the build executes.
• Output collection for projects and streams are atomic.
• Output collection in deployment areas will create a new area version.
• Build/Impacted targets calculation is based on deployment area contents –
not just the project.
• Build/Impacted targets rewritten for performance.
• Build targets optional on BLD command – will be added by server
automatically at build execution time.
34
SERENA SOFTWARE INC.
Promotion exécutée sur commande “Action”
• Implemented as a Dimensions event trigger based on the post-event for
items, requests, and/or baselines.
• As a post-event, the action will succeed even if the promote/demote fails – it
will not be atomic.
• Mappings between lifecycle states and GSL stages supported in Admin
console.
35
SERENA SOFTWARE INC.
Deployment Guide
• Introduction to Deployment
• Managing Deployment
• Deployment Scenarios
• Configuring an Environment
• Deployment Server
• Deployment Privileges
• Deployment videos coming
• www.serena.com/serenacourseware
36
Toutes les autres
nouveautés
37
SERENA SOFTWARE INC.
Amélioration des intégrations
Visual Studio et Eclipse
38
SERENA SOFTWARE INC.
Integration Visual Studio–possibilité de
choisir le mode Pessimistic locking
• Always supported explicit pessimistic locking in Projects
• Implicit modifications used “pragmatic” locking
•
•
•
•
Adding files to project
Changing project flags
Editing file
File locally modified and “Revise Item” performed on check-in
• Check-out before modification can now be enforced
• Server setting
• Dm.cfg
• DM_VISUALSTUDIO_PESSIMISTIC Y
• Applies to all users in Dimensions Projects using the server
• Implicit operations will now prompt to checkout before making the change
39
SERENA SOFTWARE INC.
IntegrationVisual Studio –
Locking dans les streams
• Locking in Streams now supported from Visual Studio
• Reuses checked-out icon from Projects in Streams
• Current user Lock is red Check mark
• Blue Padlock is standard Visual Studio Controlled file
• Other user Lock is red Check + exclamation mark
40
SERENA SOFTWARE INC.
Integration Visual Studio–
Autres améliorations
• Deployment Support
• Invokes Web Client Deployment View
• Add Solutions containing controlled projects to source control
• Previously disallowed
• Pre-requisites
• All in same Dimensions Project or Stream
• Compatible paths
• Re-open from Source Control for consistent Dimensions metadata
• Out of Project Files
• Are now fetched on open from Source Control
• Previously had to use Desktop Client and Set Bindings
• Performance
• A number of performance improvements have been made
• Reduce server interaction
• Caching of Hierarchy - Improves menu responsiveness
41
SERENA SOFTWARE INC.
Integration Eclipse–
Locking dans les streams
• Locking in Streams now supported from Eclipse
• Blue Padlock Locked , Brown Locked other , Black something Locked
42
SERENA SOFTWARE INC.
Integration Eclipse–
Support de Wind River Workbench
• Wind River Workbench
• Development Environment for Embedded systems/ RTOS
• Eclipse Based
• Customized Project View
• Hierarchical Projects Display
• WindRiver specific
• WindRiver Hierarchy Support
• Added “Recursive” operations
• Only enabled in WindRiver Workbench
• Use hierarchy to select projects for operation
• Switch to Stream (Recursive)
• Switches selected projects to corresponding project in Stream
• Synchronize with Repository (Recursive)
• Invokes synchronize view on selected projects
43
SERENA SOFTWARE INC.
Integration Eclipse–
support de Wind River Workbench
44
SERENA SOFTWARE INC.
Integration Eclipse–
Autres améliorations
• Deployment Support
• Invokes Web Client Deployment View
• Cross Stream Merging
• When Eclipse Project switched to “Non-Home” stream
• Verified incoming changes only
• Avoids resurrection of item removed in Home stream
• Same semantics as Synchronize tool
• Priming of Requests
• Now propagates related Design Part and Project/Stream
• Performance improvements in Serena Explorer
• Expanding nodes much faster
45
SERENA SOFTWARE INC.
Web services et évènements ALF
• New deployment functionality
• Other Web Services and ALF
Events:
• Promote Item/Request/Baseline
WS and ALF Event
• RunCommand WS
• Deploy Item/Request/Baseline WS
• listScheduledJobs WS
and ALF Event
• Schedule Job Complete ALF
• Demote Item/Request/Baseline
Event (CM2009R2.02)
WS and ALF Event
• Build Submitted Project ALF
• Rollback Item/Request/Baseline
Event
WS and ALF Event
• Build Completed Project ALF
• Rollback Area Version ALF event
Event
• Build Submitted Baseline ALF
Event
• Build Completed Baseline ALF
Event
46
SERENA SOFTWARE INC.
Sub-topic
Dashboards et améliorations de
l’interface Web
47
SERENA SOFTWARE INC.
Dashboards –
première impression
48
SERENA SOFTWARE INC.
Dashboards –
Quelle technologie ?
• In this release, the dashboard is a client report that has been set as
your “Home view” in the Web Client
• Additionally, a new class of client report: the “multi-view report”
has been added (in the Web Client only) and will work well as a
“Home view” report
• Basically a mosaic of other client reports laid out in a grid
• The “Home view” (or personal dashboard) can be changed in the
User Preferences dialog, but also when creating or editing a client
report (just a Set as Home view checkbox in the report dialog)
• The “Home view” (or personal dashboard) can be quickly accessed
at any time by pressing the Home link in the Web Client toolbar
• To make this work well (for example, a multi-view report that
shows request and item sub-reports), client reports are now in a
separate tab in the Web Client
49
SERENA SOFTWARE INC.
Dashboards –
Créer un rapport “Multi-vues”
50
SERENA SOFTWARE INC.
Dashboards –
Puis le définir comme “home page”
51
SERENA SOFTWARE INC.
Dashboards –
Cliquer “Home” pour l’afficher
52
SERENA SOFTWARE INC.
Améliorations de l’interface Web –
Une selection…
• Over 103 customer defects and enhancements
• Deployment views, improved area assignment to projects
• Browsing MVS deployment or work areas
• Locking files in a stream
• Improvements to Update and Deliver dialogs (with streams)
• Improvements (consistency) to Run Build and Show Impacted Targets
dialogs (now wizards)
• Administration Console has consistent look & feel with the Web Client
(and both the Administration Console & the Web Client use fewer
applets)
53
SERENA SOFTWARE INC.
Améliorations de l’interface Web –
Verrouiller des fichiers dans un Stream
54
SERENA SOFTWARE INC.
Améliorations de l’interface Web –
mise à jour depuis un autre Stream
55
SERENA SOFTWARE INC.
Améliorations de l’interface Web –
Wizards “Run Build” et “Show Impacted Targets”
56
SERENA SOFTWARE INC.
Améliorations de l’interface Web–
Cohérence de l’interface d’Administration
57
SERENA SOFTWARE INC.
Amélioration de l’interface
Windows (Desktop client)
58
SERENA SOFTWARE INC.
Amélioration du Desktop –
Principales améliorations
• Parallel development:
• Cross Stream Merging improvements
• View/ignore Deliver conflicts
• Item locking in streams – Windows Explorer
• Completely redesigned Item History dialog
• New Build and Impacted Targets wizards instead of dialogs
• MVS Area Browser
59
SERENA SOFTWARE INC.
Amélioration du Desktop –
Fusion de Stream (1/2)
5
Mainline stream
Java
Sources
Scripts
Scripts
3rd-party
3
Scripts
Scripts
6
2
Deliver
3rd-party
Major
Release
team
Get
1
8
3rd-party
Patch stream
Scripts
Scripts
Changes
Merge (Update)
Java
Sources
4
7
2009 R2 behavior
12.1 behavior
Not merged from the Patch, so it
redundantly exists in the Mainline
Deletion is merged from the Patch, so “3rd party”
does not longer exist in the Mainline.
Renamed Java
Sources in the Mainline
Reverted to their old names
and locations during the merge
The Mainline renames are preserved/not affected
with old names during Update from the Patch.
Deleted Scripts
from the Mainline
Mistakenly recreated while
merging from the Patch
Script additions are ignored while merging from
the Patch, though user can still accept recreation.
Deleted 3rdparty
from the Patch
60
3rd-party
Scripts
Scripts
SERENA SOFTWARE INC.
Amélioration du Desktop –
Fusion de stream (2/2)
Available in the following clients:
• Synchronize Wizard:
• Desktop Client
• Windows Explorer integration
• Visual Studio integration
• Eclipse integration
• Command line:
• DMCLI
• DM
User can override default behavior of merging changes verification:
• Synchronize Wizard: Using global change types filtering
(Additions/Deletions/Moves/Renames) or on per-file basis (Accept/Ignore)
• DMCLI: UPDATE /[NO|FORCE]ADD /[NO|FORCE]DELETE
• DM: update --[force|no]-add --[force|no]-delete
61
SERENA SOFTWARE INC.
Amélioration du Desktop –
Verrouiller et Livrer (Deliver) des conflits
62
SERENA SOFTWARE INC.
Amélioration du Desktop –
Wizards Build & Impacted Targets
63
SERENA SOFTWARE INC.
Amélioration du Desktop –
Item History
• Integration into Windows Explorer
• More information:
• New columns (Project(s), Stream(s), Request(s), Change Type)
• Additional change types (Import into and Removal from a stream/project)
• Improved usability:
•
•
•
•
•
Filters (from/to date filter, change type, any column “contains” filter)
Column customization
Any column sorting
Multi-line comment
Settings, size and position persistence
• New functionality:
• Open selected revisions in new window
• Compare selected revisions
• Invoke a Pedigree
64
SERENA SOFTWARE INC.
Amélioration du Desktop –
MVS area browser
<Screen-shot TBD>
65
SERENA SOFTWARE INC.
Questions ?
66
SERENA SOFTWARE INC.

similar documents