Mobile App Quality Roadmap for DevTest Teams

Editor's Notes

• #3: Submit questions using the Q&A panel. We try to answer all questions during and after the presentation. Our experts do not have access to the chat interface Participate in the polls Your participation is critical to a relevant, meaningful discussion. Watch your email for a copy of the recording and slides Today’s presentation will be recorded and sent to you. Complete the survey following the presentation Your feedback helps us provide educational tools like this webinar.
• #5: http://www.flickr.com/photos/andreasnilsson1976/1307180278/sizes/l/in/photostream/ slipping release due to long time finalizing quality. 
• #16: Continuous Delivery needs to be managed by a robust automation engine. The Automation engine must orchestrate the full CD pipeline including execution of each stage of the pipeline and the best of breed DevOps tooling used within each stage. Developers can simply focus on creating code. When they check in code to the Source Code Control System, the CD automation engine will see that check-in, pull the code out, run the application compile and build process, execute and monitor unit tests and functional tests, possibly deploy to a staging environment and then run user acceptance tests and then, if desired, the CD automation engine can even automatically deploy to production. (Automatic deployment to production is optional as not every organization is ready for that. However, Continuous Delivery means that there will always be production-ready code available to push to production when appropriate.) A enterprise-ready CD automation engine will need to have three characteristics: 1) It needs to be able to create and manage complex, real-world CD Pipelines. These are pipelines that may not be just linear sequential steps. There may be parallel branches for parallel testing, there may be loops and restarts, and there may be a need for human-intervention within the pipelines. The automation engine needs to support all of these. 2) Continuous Delivery often is applied to not just the application code but the actual environment that the application runs in as well. This means defining the application environment configuration (OS parameters, etc) “as code” and managing that “configuration-as-code” through the CD Pipeline along with the Application code. This helps insure that the application will perform exactly in production as it did in Dev and Test. 3) The last characteristic of an enterprise CD automation engine is that it needs to have the capabilities expected of enterprise software including the ability to run in an HA, or highly available, configuration. Since the CD Pipelines are touching production systems and are automating the path to production, the CD Automation engine needs to be HA. So, how can we do CD?
• #17: Jenkins is open source software that was originally developed over 10 years ago.
• #18: Here are some really cool features in Jenkins Workflow. SAs talk here about coolness of Workflow.
• #19: As we said, CD involves creating Pipelines for application code. This means that for every code “check-in” by every developer, the new code needs to go through the Pipeline that will take it from Dev to Prod. So, the CD Platform needs to manage the execution of many of these Pipelines. And the pipelines can be complex. They may have decision points or branches. They may need to be paused or restarted. Modeling the real-world process of application delivery requires that these pipelines be robust, flexible and powerful.
• #20: The CloudBees Jenkins Platform also provides a dashboard that shows the current state of the pipeline activity, such as this example, which is critical to providing a full understanding of how things are performing.
• #30: CloudBees Jenkins Platform Enterprise Edition: For Enterprise DevOps or Infrastructure teams that want to: Run Jenkins operations @scale to support a large number of developers and/or teams Optimize the performance and efficiency of the CD platform Monitor usage and share resources across their Jenkins implementation Have access to Jenkins support experts for quick problem resolution Ships with All Advanced Enterprise Features for both: CloudBees Jenkins Enterprise CloudBees Jenkins Operations Center CloudBees Jenkins Platform Team Edition: For small Dev teams or organizations with a limited number of developers that want to: Improve developer productivity by leveraging advanced developer features for Jenkins Easily get started with continuous integration (CI) and continuous delivery (CD) Have access to Jenkins Support experts for problem resolution Ships with a starter-pack of Enterprise Features focused on Developer Productivity: Developer Productivity Improved developer feedback loop and eliminate downtime with Validated Merge for Git and GitHub Pull Request Team Management Organize teams with folders Recoverability from failures using backup Security Roles-based access control Isolate team-sensitive slaves Analytics Build and performance dashboards Support Module Faster diagnosis for production issues