1 / 66

Serena Dimensions CM 12.1

Serena Dimensions CM 12.1. Agenda. Introduction : évolution s 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. Evolution du marché de la GCL.

avery
Download Presentation

Serena Dimensions CM 12.1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Serena Dimensions CM 12.1

  2. Agenda • Introduction : évolutions du marché de la GCL • Principalesnouveautés de Dimensions CM 12.1 • Thème principal : gestion des déploiements • Toutes les autresnouveautés • Questions

  3. Evolution du marché de la GCL

  4. L’adoption des méthodesAgiles continue de progresser

  5. Les motivations pour adaopteruneméthode Agile Pas simplement de l’efficacité pour les développeursmais des objectifs plus stratégiques

  6. La satisfaction vis à vis du processus de déploiementestbasse

  7. Principalesnouveauté de Dimensions CM 12.1

  8. Dimensions CM – Les processus GCL Couverts Gestion du Changement Change Requests, Issue Tracking, Audit Control Process and Workflow Control Gestion de Configuration Version Control, Stream Management, Baseline Management Processus GCL Globaux Automation, Traceability, Enforcement Gestion de fabrication Continuous Integration, Impact Analysis, Build Automation Gestion des Déploiment (Release) Packaging, Deployment, Acceptance testing

  9. Roadmap and Platform Matrix http://roadmap.serena.com/

  10. Les nouvellesfonctions de Déploiement SERENA SOFTWARE INC.

  11. Agenda • Pourquoiaméliorer les fonctions de déploiement • Revue des nouvellesfonctionnalités • Aperçu en “live” SERENA SOFTWARE INC.

  12. La satisfaction vis à vis du processus de déploiementestbasse

  13. Comparaison des fonctionnalités SERENA SOFTWARE INC.

  14. Comparaison des fonctionnalités (suite) SERENA SOFTWARE INC.

  15. Revise An Item Initial Stage Revise 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)

  16. Revise An Item with Selected Areas Initial Stage Revise foo.c;5 foo.c;5 DEV1 DEV2 foo.c;5 DEV3 • 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)

  17. Promote Item Revise foo.c;5 Promote foo.c;5 Initial Stage ST foo.c;5 DEV1 ST1 DEV2 ST2 foo.c;5 ST3 DEV3 ST4 • Sets the item revisions Stage attribute to ST • Does not deploy any items (no Areas selected)

  18. Promote Item With Area Selection Revise foo.c;5 Promote foo.c;5 Initial Stage ST foo.c;5 foo.c;5 DEV1 ST1 DEV2 ST2 foo.c;5 foo.c;5 ST3 DEV3 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)

  19. Promote Item Beyond The Next Stage Revise foo.c;5 Promote foo.c;5 Initial Stage REL ST foo.c;5 foo.c;5 foo.c;5 DEV1 REL1 foo.c;4 ST1 foo.c;5 DEV2 REL2 ST2 foo.c;5 REL3 DEV3 foo.c;4 ST3 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

  20. Deploy An Item Revision Revise foo.c;5 Initial Stage foo.c;5 DEV1 foo.c;4 DEV2 foo.c;5 DEV3 • 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

  21. Deploy An Item Revision Revise foo.c;5 Initial Stage ST foo.c;5 DEV1 ST1 foo.c;4 foo.c;5 DEV2 ST2 foo.c;5 ST3 DEV3 ST4 • Only allowed if the Item Revision is at that Stage

  22. Deploy An Item Revision Revise foo.c;5 Promote foo.c;5 Initial Stage ST foo.c;5 foo.c;5 DEV1 ST1 foo.c;4 foo.c;5 DEV2 ST2 foo.c;5 foo.c;5 ST3 DEV3 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

  23. Deploy A Previous Item Revision Revise foo.c;5 Promote foo.c;5 Initial Stage ST foo.c;5 foo.c;5 DEV1 ST1 foo.c;4 foo.c;4 foo.c;5 DEV2 ST2 foo.c;5 foo.c;5 ST3 DEV3 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

  24. Deploy A Previous Item Revision Revise foo.c;5 Promote foo.c;5 Initial Stage ST foo.c;5 foo.c;5 DEV1 ST1 foo.c;4 foo.c;5 foo.c;4 DEV2 ST2 foo.c;5 foo.c;4 foo.c;5 ST3 DEV3 ST4 • Deploy can deploy to any areas under a Stage

  25. Actioning Requests New Assigned Dev Complete In ST • New Request • Assigned to developer Stage: ST CR_1 • Developer revises Item against Request Areas: ST1, ST2 & ST4 Areas: ST1 Revise foo.c;5 Promote foo.c;5 • Developer Actions Request Initial Stage ST • QA Actions Request To “In ST” State • User adds Areas ST2 & ST4 to ST1 which is automatically selected foo.c;5 DEV1 ST1 foo.c;5 DEV2 ST2 foo.c;5 • Issues Promote To “ST” State and Deploys to ST1, ST2 & ST4 foo.c;5 ST3 DEV3 ST4 foo.c;5

  26. 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

  27. 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

  28. 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

  29. 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. SERENA SOFTWARE INC.

  30. 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. SERENA SOFTWARE INC.

  31. Nouvellesproprié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. SERENA SOFTWARE INC.

  32. 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. SERENA SOFTWARE INC.

  33. 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. SERENA SOFTWARE INC.

  34. 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. SERENA SOFTWARE INC.

  35. Promotion exécutéesurcommande “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. SERENA SOFTWARE INC.

  36. Deployment Guide • Introduction to Deployment • Managing Deployment • Deployment Scenarios • Configuring an Environment • Deployment Server • Deployment Privileges • Deployment videos coming • www.serena.com/serenacourseware

  37. Toutes les autresnouveautés SERENA SOFTWARE INC.

  38. Amélioration des intégrations Visual Studio et Eclipse SERENA SOFTWARE INC.

  39. 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 SERENA SOFTWARE INC.

  40. IntegrationVisualStudio –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 SERENA SOFTWARE INC.

  41. Integration Visual Studio–Autresamé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 SERENA SOFTWARE INC.

  42. Integration Eclipse–Locking dans les streams • Locking in Streams now supported from Eclipse • Blue Padlock Locked , Brown Locked other , Black something Locked SERENA SOFTWARE INC.

  43. 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 • WindRiverHierarchy 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 SERENA SOFTWARE INC.

  44. Integration Eclipse–support de Wind River Workbench SERENA SOFTWARE INC.

  45. Integration Eclipse–Autresamé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 SERENA SOFTWARE INC.

  46. Web services et évènements ALF • New deployment functionality • Promote Item/Request/Baseline WS and ALF Event • Deploy Item/Request/Baseline WS and ALF Event • Demote Item/Request/Baseline WS and ALF Event • Rollback Item/Request/Baseline WS and ALF Event • Rollback Area Version ALF event • Other Web Services and ALF Events: • RunCommandWS • listScheduledJobs WS • Schedule Job Complete ALF Event (CM2009R2.02) • Build Submitted Project ALF Event • Build Completed Project ALF Event • Build Submitted Baseline ALF Event • Build Completed Baseline ALF Event SERENA SOFTWARE INC.

  47. Sub-topic Dashboards et améliorations de l’interface Web SERENA SOFTWARE INC.

  48. Dashboards –première impression SERENA SOFTWARE INC.

  49. Dashboards –Quelletechnologie ? • 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 SERENA SOFTWARE INC.

  50. Dashboards –Créer un rapport “Multi-vues” SERENA SOFTWARE INC.

More Related