Tce automation-d4-110102123012-phpapp01

Editor's Notes

• #3: Manual & Repetitive tasksDevelopmentQAOPSWhat do we automate ? – Everything, development, build, deployment …How can automation help ? - Who automates ? - parties participating in automationWhen do we automate ? – an open question for the last slide
• #4: People & DemandsClient demands are changingWe are all clients within and out the organizationpeople are changing = usTechnologies are changingOrganizations are changingPeople & DemandsTechnologiesOrganizations
• #5: Business processesAutomate repetitive time consuming tasks
• #6: All parties in the organizationWe are changing thus we are the leaders of the change
• #7: Now – if we want our customer to stay we need to make necessary adjustments
• #8: Are there things we can do betterHow are our executionsWe have lessons learned do we apply them into out processes or just keep having these meetings? Voer & overContinuousbuilds => continues testing => continuous deploymentWe have virtualization / Grid => lets take them to the EXTREAME – stretch our abilitiesImprove collaborationRevise & Reuse processesUtilize existing assetsImprove collaboration across teams & divisions
• #9: DevelopmentQAConfiguration Management / Release managementThere is Something missing in here …
• #10: Working together end 2 end delivering continuous valueAutomation is a set of processes, methods and systems for communication, collaboration and integration between departments for Development (Applications/Software Engineering), Technology Operations and Quality Assurance (QA). It relates to the emerging understanding of the interdependence of development and operations in meeting a business' goal to producing timely software products and servicesOps are “left behind”Decision takers / risk assent done in late stages Dev, QA, CM, OPS
• #12: The funnel driving modules / features from Development through QA & CM to Operations
• #13: There are quite a fewShort overview will follow …
• #14: The key to automation – nothing without X testingUnit testing – short and to the pointDo not mix-up with system / integration testing’
• #15: Tests your code as part of a bigger systemDevelopers better aware of the bigger picture
• #16: GUIUsabilityPerformanceOS’sInstaller(s) and more …Jsystem / QTP – QA role
• #19: Missing data
• #21: BuildGenerate reportsQuick Feedback to DevProve continuous stability
• #22: BuildGenerate reportsQuick Feedback to DevProve continuous stability
• #23: As described in Eishay’s (smith) presentationsWe have atested module / component ready for deployment
• #25: The range of technologies available in each layer are big how do we choose – criteria based on Answers CI’s needs SCM “easy merging” - gitOne mainline – subversion We saw the ability of utlizing SVN’s capabilities and Git powerful merging in previous presentationBuild Tools Ant – free style all the way …Maven - xml based, fixed lifecycle expandable via pluginsGradle, Buildr – very much like Maven in terms of dependency mangmnet language driven Auto builder - Continuous builds CM & developer (multiple views) = hudsonSupport / extend support of our build toolOn submit / scheduledAutomatic deploymnet via promotions vs separate “out of context builds” in other Auto Builders (mentioned above)Cloud integration (ssh, libvirt, pre post vm actions)
• #26: The range of technologies available in each layer are big how do we choose – criteria based on Answers CI’s needs SCM “easy merging” - gitOne mainline – subversion We saw the ability of utlizing SVN’s capabilities and Git powerful merging in previous presentationBuild Tools Ant – free style all the way …Maven - xml based, fixed lifecycle expandable via pluginsGradle, Buildr – very much like Maven in terms of dependency mangmnet language driven Auto builder - Continuous builds CM & developer (multiple views) = hudsonSupport / extend support of our build toolOn submit / scheduledAutomatic deploymnet via promotions vs separate “out of context builds” in other Auto Builders (mentioned above)Cloud integration (ssh, libvirt, pre post vm actions)
• #33: שלום קוראים לי איתיואני ידגים לכם את מה שחגי דיבר עד עכשיואוטומציה של התהליכים בתוך ארגוןלצורך ההדגמה מדובר בחברת מוצר שמיצרת Distrebution of hudson Build manager אני יציג תהליך של בנית PluginPromotedSimplePluginהרחבה של hudson promote pluginיצירת ditrebution of hudson in servletcontiner (tomcat)With the promoted pluginלצורך זה אני ישתמש בHudson – build managerNexus – artifatreporitoryMaven – build scripts
• #36: שלום קוראים לי איתיואני ידגים לכם את מה שחגי דיבר עד עכשיואוטומציה של התהליכים בתוך ארגוןלצורך ההדגמה מדובר בחברת מוצר שמיצרת Distrebution of hudson Build manager אני יציג תהליך של בנית PluginPromotedSimplePluginהרחבה של hudson promote pluginיצירת ditrebution of hudson in servletcontiner (tomcat)With the promoted pluginלצורך זה אני ישתמש בHudson – build managerNexus – artifatreporitoryMaven – build scripts
• #49: The key to automation – nothing without X testingUnit testing – short and to the pointDo not mix-up with system / integration testing’