Continuous delivery for Android

Sep 16, 20161 like428 views

Continuous delivery is a software development discipline where you build software in such a way that the software can be released to production at any time. The idea is to make your software releasable at any moment of time by integrating it continuously and releasing it frequently to get early and frequent feedback. Because of the approval process that exists in the release process of Android apps, Continuous Delivery is not easy for Android apps as compared to web application deployments. And it's also assumed that not much tools are available to enable Continuous Delivery. Yes, its still not instant update to the app, but still things are better than how it has been in the past. This talk gives an overview of tools and techniques that can help us to create a pipeline to get fast and frequent feedback through continuous delivery.

Continuous Delivery
for Android
By @leenasn

Agenda
● Why Continuous Delivery
● Continuous Delivery for Android Apps - Challenges
● Overview of the Tools

Building something nobody wants is
the ultimate form of waste
~Eric Ries
The Lean Startup

Think about how long would it take you to
deliver a change of one line of code within
your application to production
~Mary and Tom Poppendieck
Lean Software Development, An Agile Toolkit

https://www.infoq.com/articles/standish-chaos-2015

Continuous Delivery
“Continuous Delivery is a software development discipline where
you build software in such a way that the software can be
released to production at any time.”
http://martinfowler.com/bliki/ContinuousDelivery.html

Continuous Integration
“Continuous integration (CI) is the practice, in software
engineering, of merging all developer working copies to a shared
mainline several times a day.”

https://twitter.com/mobileapptimize/status/713441244639281154

http://cnmnewz.com/wp-content/uploads/2014/06/Golden-Gate-Bridge-with-Net-AP.jpg

Case Studies
http://mobiledeliverydays.org/program/

https://github.com/multunus/android-sample-app

1. http://martinfowler.com/articles/feature-toggles.html
2. http://www.multunus.com/blog/2016/03/merge-hells-feature-toggles-resc
ue/
3. http://www.slideshare.net/TimothyFitz/continuous-deployment-beyond-c
ontinuous-delivery
4. http://blog.crisp.se/2013/02/05/yassalsundman/continuous-delivery-vs-co
ntinuous-deployment
5. https://gradle.org/case-study-continuous-delivery-netflix/
6. http://mobiledeliverydays.org/program/
References

Leena S N
@leenasn / leena.sn@multunus.com

A quick presentation comparing the main five test automation frameworks: Record and Playback - Data Driven - Keyword Driven - Function Driven - Behaviour Driven Then presentation separates the frameworks into generation 1 to 3 and rates them against the goal of test automation. 1. Improve Software quality 2. Early detection of bugs (Defects) 3. Reduce (not introduce) project risk 4. Easy to write and maintain by BA, Testing and technical resources 5. Reduced cost and time of development

From 0 to DevOps: Lessons Learned Moving from On-Prem to Cloud NativeKlaus Enzenhofer

This document discusses the transition from on-premise software development to cloud native development. It outlines how Dynatrace has transformed its development process, increasing the number of releases per year from 2 to 26 and the number of code commits and tests performed. This allows for faster innovation, immediate feedback, and more stability. It advocates adopting a DevOps model with continuous delivery and feedback across development, testing, and production stages. All stages should use the same automation and orchestration layer to reduce manual touches and ensure consistency. The goal is for development teams to own the full lifecycle of their features.

Tales from the Dark Side: Ori Bendet Selenium Conference India 2016Ori Bendet

Agile Project Managementmjansen

DevOps at Lean AppsLean Apps

Continuous integration John Temoty Roca

Continuous integration is a development practice that requires developers to integrate code into a shared repository multiple times a day, with each check-in verified by an automated build to detect problems early. Continuous integration differs from continuous delivery, which aims to deliver high quality software quickly, and continuous deployment, which automatically releases software passing automated tests into production. Continuous integration brings benefits like reducing integration issues and allowing faster software delivery by catching issues early.

continous integration and deliverySamarjeet Saurabh

This document discusses continuous integration (CI), continuous delivery (CD), and DevOps. It defines CI as integrating code changes frequently, such as daily, and verifying them through automated builds and tests. CD builds on CI by making software deployable at any time by prioritizing deployments over new features and enabling anyone to deploy any version on demand. For developers, CD provides immediate feedback and the ability to test in production-like environments. For system admins, CD allows automating environments for developer testing. For businesses, CD lowers deployment risks and improves market responsiveness.

Continous Integration: A Case StudyTalentica Software

One of the challenges faced by many web development based projects is the integration of source code for multiple releases during parallel development. The task to build and test the multiple versions of source code can eat out the quality time and limit the efficiency of the development/QA team. The case study focuses to resolve the issues of extensive effort consumed in build and deployment process from multiple branches in source repository and aim at Identification of source code integration issues at the earliest stage. This can further be enhanced to limit the manual intervention by integration of build system with test automation tool. The above can be achieved by using different CI tools (like Hudson/Bamboo/TeamCity/CruiseControl etc) for continuous build preparation and its integration with any test automation suite. The case study specifies the use of CI-Hudson tool for continuous integration using ANT tool for build preparation and further invoking the automation test suite developed using selenium. It also discusses the limitations and challenges of using such an integration system for testing a web based application deployed on Apache Tomcat server. It also details additional plugins available to enhance such an integration of multiple systems and what can be achieved using the above integration.

How to Measure Success in Continuous Testing by Fernando Vidal and Amir Rozen...Sauce Labs

In this SauceCon 2019 talk, Fernando and Amir use observations from running 2 billion tests for thousands of Sauce Labs customers to outline the the key drivers of success in continuous testing and an provide an actionable way to see how organizations are doing relative to other successful testers. They discuss a new index which can be used by any organization to evaluate their progression towards continuous testing, and cover the components of the new continuous testing index, what makes these components such strong maturity indicators, how organizations can improve on each of the metrics, and what happens organizationally when those metrics are improved

CI/CT/CD and Role of Quality EngineeringSushma

The document discusses continuous integration, continuous testing, and continuous delivery (CI/CD). It notes that CI/CD aims to continuously release quality code to production with confidence. It also discusses that tools, processes, and people are critical parts of the CI/CD model. The document then outlines Intuit's journey to implement CI/CD across its organization over multiple years to improve software delivery.

DevOps - From Agile Dev to Agile Ops for Continuous DeliveryKalyan Kumar

This document discusses moving from a traditional development and operations model to a DevOps model using continuous delivery. It outlines some anti-patterns to avoid when adopting DevOps, such as treating configuration management as DevOps or creating separate DevOps teams. The traditional model has development and operations teams with different goals and tools working independently. Continuous delivery is presented as an Agile approach where development, testing, deployment, and monitoring are automated and continuous. This allows for faster and more reliable software releases.

Testing in a continuous delivery environmentStefan Verhoeff

Appium vs Espresso and XCUI TestPerfecto by Perforce

The rise of DevOps and the increase in developer-QA collaboration has led to the introduction of new testing frameworks such as Espresso and XCUITest. Join us and learn how organizations are improving pipeline efficiency by adding Espresso to their CI process as well as learn the basic concepts of instrumented test tools such as Espresso and XCUITest. This webinar will cover: -Latest market trends causing this shift and why organizations are moving from Appium to Espresso -For each framework (Espresso, XCUITest and Appium), we will cover: -Characteristics -Technology/Architecture -Pros & Cons -Demo of Espresso

How Vanguard Got to a CD-CD World by Craig SchwarzwaldSauce Labs

In this SauceCon 2019 presentation, Craig Schwarzwald discusses the main phases Vanguard software testing has undergone over the last 10+ years, from thousands of manual tests, to thousands of automated tests with Selenium, to Shifting Left, and to now focusing on Contract Testing. He discusses what Contract Testing is and talks about its importance in the CI/CD pipeline (giving the team virtually E2E coverage at the speed of Unit tests).

DevOps - Overview - One of the Top Trends in IT IndustryRahul Tilloo

DevOps is a software development methodology that emphasizes communication and collaboration between software developers, testers, and IT professionals. It aims to shorten the systems development life cycle and provide continuous delivery with high software quality. DevOps incorporates culture, automation, measurement, sharing, and lean/agile principles. It addresses gaps between development and operations teams. Benefits include faster delivery, more stable environments, improved collaboration, and increased innovation.

Introducing Continuous Integration Using VstsMohamed Samy

ETDP 2015 D2 Do it-yourself dynamics – vibration assessment using smartphones...Comit Projects Ltd

Pete Winslow and James Parker, Expedition Engineering In past years much progress has been made to demystify the issue of ‘vibrations and dynamics’. Well established methods of advanced analysis and testing are now available to practicing engineers to assess and verify performance – for both construction vibrations and for performance of the as-built structure itself. However, physical testing of vibrations still remains an area reserved for specialists, and it is generally only undertaken if an obvious problem has arisen. Traditional instrumentation/measurement approaches can have long lead times, are time-consuming and costly. During the presentation we will live-demonstrate the “Vibrate-it” testing app for floor vibrations, which has been developed by Expedition and is free-to-download. A discussion of potential future uses will follow, including benefits, pitfalls and hints for others that may be interested in this emerging field.

Continuous testing for devopsSubrahmaniam S.R.V

Overview the Challenges and Limitations of Android App Automation with Espres...Sauce Labs

DevOps Overview in my own wordsSUBHENDU KARMAKAR

Usg Web Tech Day 2016 - Continuous Integration, Deployment, and DeliveryStephen Garrett

Brief oncontinuousperformancetestingKriti Mehta

The document discusses the importance of continuous performance testing and establishing a process for it. It describes common issues that arise when performance testing is left until late, such as increased costs, decreased productivity, and damaged customer relations. It then outlines a seven step process for continuous performance testing, including including performance in requirements, regularly conducting performance tests, constantly monitoring performance, and using performance data to efficiently tune problem areas of code.

Automated Testing at The Speed of Headless by Alissa Lydon and Samantha CoffmanSauce Labs

In this SauceCon 2019 presentation, Samantha Coffman, Product Manager at Sauce Labs, and Alissa Lydon, Product Marketing Manager at Sauce Labs, discuss Sauce Headless, the industry’s first cloud-based headless testing solution, making it a fast and affordable option for early pipeline testing at scale. They will cover the benefits of using Sauce Headless in conjunction with Sauce Labs traditional VM offering to increase the release velocity, as well as examples of customers who are experiencing upwards of 50% faster test times using Sauce Headless.

Introduction to DevOpsRavindu Fernando

DevOpsRavneetArora

DevOps aims to harmonize development and operations to facilitate continuous delivery. It involves continuous integration (CI), where code is integrated into a shared repository multiple times daily and automatically built/tested, and continuous deployment (CD), where software can be reliably released at any time through short development cycles. Visual Studio Team Services (VSTS) helps with build and release management through features like Git, build definitions, and release management to deploy to Azure.

State of mobile Continuous Delivery at SpotifyMobile Delivery Days

Dawn of the DevOps - TJ Randall - EMC World 2015XebiaLabs

This document summarizes a presentation about implementing DevOps changes in organizations. It discusses facing fears and reactions when trying to implement organizational change. It describes the three types of applications in enterprises and how continuous delivery can benefit all applications. It addresses forces that prevent DevOps success and provides steps to implement true continuous delivery. The presentation aims to help audiences better implement DevOps changes to achieve organizational goals.

Software Craftsmanship - It's an ImperativeFadi Stephan

The document discusses the history and principles of software craftsmanship. It outlines how software craftsmanship values not only working software but well-crafted software, and focuses on steadily adding value through a community of professionals. The document presents the Manifesto of Software Craftsmanship and its emphasis on technical excellence, good design, automation, clean code, and continuous improvement.

Merge hells!! feature toggles to the rescue - Presented @ Agile TorontoLeena N

Have you ever wondered how Amazon does deployments in every 11 seconds? Have you ever wondered how frequently Google Chrome updates? Compare that with an enterprise product you are using or the banking application that you use, it takes weeks or even months for an update. The assumption is that frequent releases are possible for Googles or Amazons or Unicorns. It is not for others. This talk is about why that assumption is wrong. It can be done anywhere, with enough focus and investment for the Continuous Delivery pipeline to make sure that every commit is releasable or deployable. And fundamental to Continuous Delivery is Continuous Integration. Continuous Integration guarantees every change committed to the repository is tested and reported about production readiness. And Feature Toggle is for turning features on/off depending upon certain conditions. This opens the opportunity to test certain features quickly with few users for experimentation and learning. Feature branching has been popular for long, but everyone knows about the “code merge hell”, a common issue because of long-lived branches or infrequent integration. If the team is spending time in fixing the merge hells and checking what part of the code needs to be merged, then it is not the efficient use of human talent.

Merge hells!! feature toggles to the rescueLeena N

Introducing Continuous Delivery practices to a team in trouble can be daunting. Where do you start ? What do you do first ? Which battle do you pick first ? I’ll share my experience of guiding a team to achieve a higher degree of delivery maturity. This is a journey from a troublesome, struggling start of chaotic manual deployments, merge hell, regular production roll backs and lost code, to deliver a single commit to trunk automatically and reliably, under an hour, many times a day.

More Related Content

What's hot (20)

How to Measure Success in Continuous Testing by Fernando Vidal and Amir Rozen...Sauce Labs

CI/CT/CD and Role of Quality EngineeringSushma

DevOps - From Agile Dev to Agile Ops for Continuous DeliveryKalyan Kumar

Testing in a continuous delivery environmentStefan Verhoeff

Appium vs Espresso and XCUI TestPerfecto by Perforce

How Vanguard Got to a CD-CD World by Craig SchwarzwaldSauce Labs

DevOps - Overview - One of the Top Trends in IT IndustryRahul Tilloo

Introducing Continuous Integration Using VstsMohamed Samy

ETDP 2015 D2 Do it-yourself dynamics – vibration assessment using smartphones...Comit Projects Ltd

Continuous testing for devopsSubrahmaniam S.R.V

Overview the Challenges and Limitations of Android App Automation with Espres...Sauce Labs

DevOps Overview in my own wordsSUBHENDU KARMAKAR

Usg Web Tech Day 2016 - Continuous Integration, Deployment, and DeliveryStephen Garrett

Brief oncontinuousperformancetestingKriti Mehta

Automated Testing at The Speed of Headless by Alissa Lydon and Samantha CoffmanSauce Labs

Introduction to DevOpsRavindu Fernando

DevOpsRavneetArora

State of mobile Continuous Delivery at SpotifyMobile Delivery Days

Dawn of the DevOps - TJ Randall - EMC World 2015XebiaLabs

Software Craftsmanship - It's an ImperativeFadi Stephan

How to Measure Success in Continuous Testing by Fernando Vidal and Amir Rozen...Sauce Labs

CI/CT/CD and Role of Quality EngineeringSushma

DevOps - From Agile Dev to Agile Ops for Continuous DeliveryKalyan Kumar

Testing in a continuous delivery environmentStefan Verhoeff

Appium vs Espresso and XCUI TestPerfecto by Perforce

How Vanguard Got to a CD-CD World by Craig SchwarzwaldSauce Labs

DevOps - Overview - One of the Top Trends in IT IndustryRahul Tilloo

Introducing Continuous Integration Using VstsMohamed Samy

ETDP 2015 D2 Do it-yourself dynamics – vibration assessment using smartphones...Comit Projects Ltd

Continuous testing for devopsSubrahmaniam S.R.V

Overview the Challenges and Limitations of Android App Automation with Espres...Sauce Labs

DevOps Overview in my own wordsSUBHENDU KARMAKAR

Usg Web Tech Day 2016 - Continuous Integration, Deployment, and DeliveryStephen Garrett

Brief oncontinuousperformancetestingKriti Mehta

Automated Testing at The Speed of Headless by Alissa Lydon and Samantha CoffmanSauce Labs

Introduction to DevOpsRavindu Fernando

DevOpsRavneetArora

State of mobile Continuous Delivery at SpotifyMobile Delivery Days

Dawn of the DevOps - TJ Randall - EMC World 2015XebiaLabs

Software Craftsmanship - It's an ImperativeFadi Stephan

Similar to Continuous delivery for Android (20)

Merge hells!! feature toggles to the rescue - Presented @ Agile TorontoLeena N

Merge hells!! feature toggles to the rescueLeena N

Merge hells!! Feature toggles to the rescue - DevOpsDays MadisonLeena N

This document discusses using feature toggles to help manage merge conflicts and allow for continuous delivery of code changes. It notes that building features nobody wants is a waste of resources. Feature toggles allow code to be deployed without being released, avoiding rollback issues. They also enable options like A/B testing and canary releasing. The document recommends managing feature toggles through configuration files and designing systems to be failure-tolerant using circuit breakers. It suggests architectures like branch by abstraction and strangler patterns to help manage feature toggles. Overall, it advocates taking a lean approach by working in small batches to integrate changes continuously.

Do's and don'ts for continuous deliveryMichael Athiwat Wongwaisayawan

This document discusses dos and don'ts for continuous delivery. It recommends automating deployment and provisioning processes, using the same mechanisms for all environments, checking all code into version control, and incrementally implementing continuous delivery practices. It also advises understanding why changes are needed, using short-lived branches, and understanding one's team capabilities.

Transform Digital Business with DevOpsDaniel Oh

1) The document discusses how DevOps practices like continuous integration, delivery, and deployment can help organizations innovate faster by getting code changes to production environments more quickly. 2) It provides examples of how some banks are transforming their development processes using Red Hat OpenShift to deploy microservices in seconds rather than months. 3) The document outlines the benefits of a continuous delivery pipeline that leverages tools like Jenkins to automatically build, test, and deploy application images to non-production and production environments with minimal manual approvals required.

Agile A to Z Chapter 4 Feedback Loop Part 2 DevOpsAgile ME

This document discusses DevOps practices for improving software development processes through feedback loops, collaboration, visibility, and shared responsibility. It covers version control, peer reviews, pair programming, unit testing, test-driven development, behavior-driven development, testing strategies, continuous integration, continuous delivery, deployment pipelines, infrastructure considerations, monitoring, analytics, performance, and security. The overall aim is to build, test, and release software faster and more reliably through automation, visibility, and collaboration between teams.

Agile a to z chapter 4 feedback loopWajih Aslam

The document discusses various DevOps practices for improving feedback loops, including breaking down silos, enabling easier collaboration, improving visibility, encouraging more engagement, sharing responsibility and ownership. It covers version control, peer reviews, pair programming, unit testing, test-driven development, behavior-driven development, testing automation, continuous integration, continuous delivery, deployment pipelines, infrastructure and virtualization, application monitoring and alerting, analytics, and application performance monitoring. The overall goal is to establish a feedback loop to find and address issues more quickly in order to improve software quality.

Continuous integration CloudParty 21 may 2014 - MilanSimone Pasquini

This document discusses continuous integration, which involves integrating code changes frequently from developers, ideally multiple times per day, and automatically testing the integrated codebase to provide quick feedback. Key aspects of continuous integration include maintaining a single code repository, automating builds, running self-testing of code through automated tests, having developers commit to the main code branch daily, automatically building and testing code on each commit, keeping the build fast, testing in the production environment clone, making the build status visible to all, automating deployments, and prioritizing fixing any broken builds. The presentation provides an example continuous integration workflow and tools used at Onebip including Phing for build automation and a deployment pipeline across different environments like CI, IT, UAT

Continuous IntegrationPreetam Palwe

Continuous Integration (CI) is a software development practice where developers integrate code into a shared repository frequently, preferably daily or multiple times per day. Each integration is verified by an automated build and test process to detect errors early. CI can significantly reduce integration problems and allow software to be developed more rapidly. CI practices include automating builds and tests, integrating frequently in small batches, treating failures as priority issues, and making current successful builds easily available. Open source tools like CruiseControl can help implement CI processes.

Transition from CI to CDNanjekye Joannah

During this talk, I’ll start by introducing continuous delivery and I will distinguish Continuous Integration from Continuous Delivery, why teams need to do continuous delivery and what is required for teams to do it. I’ll then present the principles and practices involved in continuous delivery along with the benefits in general and on a personal basis from my operations. Finally, I will wrap the talk up with a demo using one of the projects where I have used Continuous Delivery.

Building environment of #UserDevOps and not only DevOpsRajnish Chauhan

In so much of IT tools and technology we missed and forgotten the very user and requirement. If requirement are not of high quality , we can not expect the software of quality as quality is not only all about defects & bugs but also if it is usable and meeting the need of user community. There are many tools and methodology and I have detailed what minimum with one can start UserDevOps transformation and can bring values to business.

Continuous Integrationdrluckyspin

Continuous Integration (CI) is a development practice where developers integrate code changes daily with the main codebase. It helps reduce risks in software development by catching bugs early, improving team cohesion, and increasing code quality. To implement CI, teams should commit code changes frequently, have an automated build that runs tests on each change, and monitor build metrics to identify issues quickly. CI can help teams build better software faster and with more confidence.

Experitest-Infosys Co-Webinar on Mobile Continuous IntegrationExperitest

Continuous, continuous, continuousMichele Orselli

QCon'17 talk: CI/CD at scale - lessons from LinkedIn and MockitoSzczepan Faber

Learn how continuous deployment can improve your organization's productivity. Learn about challenges, differences and similarities of CD at LinkedIn (large scale enterprise) and Mockito (OSS software library with huge user base). More details: http://bit.do/qcon-cd-abstract Google slides: http://bit.do/qcon-cd-gslides Presentation abstract as in QCon session catalog: LinkedIn and Mockito are two different use cases of implementing continuous delivery at scale. Yet the challenges, benefits and impact on the engineering culture are very similar. In 2015, LinkedIn’s flagship application adopted a continuous delivery model we called 3x3: deploy to production 3 times a day, with a 3 hour maximum time from commit to production. At LinkedIn scale - hundreds of engineers building products for 500M users - implementing 3x3 was really hard. How did 3x3 change LinkedIn engineering culture and what we have learned on the way? Mockito is a top 3 Java library with ~2M users. Even with that large user base, since 2014, the Mockito project has taken the surprising approach of publishing a new version of the library from every single pull request. This approach is challenging and innovative in the Java community, and Mockito leverages Shipkit to ship every change to production. Why did the Mockito team adopt continuous delivery in 2014 and what we have learned to date? Join and learn from Szczepan Faber, the maker of Mockito framework since 2007, and the tech lead of LinkedIn Development Tools since 2015.

The Ultimate Guide_ 15 Best Continuous Testing Tools in 2024.pdfkalichargn70th171

Continuous Integration IntroductionFáber D. Giraldo

Continuous integration (CI) is a software development practice where members of a team integrate their work frequently, which can be multiple times per day. Each integration is verified by automated builds and tests to quickly detect errors. CI aims to improve quality and reduce time to deliver software. It replaces traditional quality control after development is complete. Tools like Jenkins can automate builds, tests, and deployments to help teams implement CI and evolve it into continuous delivery of software.

Agile & DevOps - It's all about project successAdam Stephensen

The document provides information on DevOps practices and tools from Microsoft. It discusses how DevOps enables continuous delivery of value through integrating people, processes, and tools. Benefits of DevOps include more frequent and stable releases, lower change failure rates, and empowered development teams. The document provides examples of DevOps scenarios and recommends discussing solutions and migration plans with Microsoft.

Continuous integration for Ruby on RailsDavid Paluy

Continuous integration (CI) is a development practice that requires developers to integrate code into a shared repository multiple times per day. Each check-in is automatically built and tested to find problems early. For Ruby on Rails projects, CI can generate code coverage reports, perform static code analysis, and document APIs. CI builds confidence by continuously integrating and testing code changes. Continuous deployment further automates software delivery through continuous integration.

CI/CD: Lessons from LinkedIn and MockitoC4Media

Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/2Gtedjh. Szczepan Faber talks about two different use cases of implementing continuous delivery at scale: LinkedIn and Mockito. Yet the challenges, benefits and impact on the engineering culture are very similar. Filmed at qconsf.com. Szczepan Faber is a Tech Lead for LinkedIn Development Tools, responsible for developer productivity at LinkedIn. Previously, he was core engineer of Gradle 1.x and 2.x. and instructed numerous classes on build automation. He created Mockito framework in 2007, currently estimated user base of 2M, and has been giving classes on automated testing since.

Merge hells!! feature toggles to the rescue - Presented @ Agile TorontoLeena N

Merge hells!! feature toggles to the rescueLeena N

Merge hells!! Feature toggles to the rescue - DevOpsDays MadisonLeena N

Do's and don'ts for continuous deliveryMichael Athiwat Wongwaisayawan

Transform Digital Business with DevOpsDaniel Oh

Agile A to Z Chapter 4 Feedback Loop Part 2 DevOpsAgile ME

Agile a to z chapter 4 feedback loopWajih Aslam

Continuous integration CloudParty 21 may 2014 - MilanSimone Pasquini

Continuous IntegrationPreetam Palwe

Transition from CI to CDNanjekye Joannah

Building environment of #UserDevOps and not only DevOpsRajnish Chauhan

Continuous Integrationdrluckyspin

Experitest-Infosys Co-Webinar on Mobile Continuous IntegrationExperitest

Continuous, continuous, continuousMichele Orselli

QCon'17 talk: CI/CD at scale - lessons from LinkedIn and MockitoSzczepan Faber

The Ultimate Guide_ 15 Best Continuous Testing Tools in 2024.pdfkalichargn70th171

Continuous Integration IntroductionFáber D. Giraldo

Agile & DevOps - It's all about project successAdam Stephensen

Continuous integration for Ruby on RailsDavid Paluy

CI/CD: Lessons from LinkedIn and MockitoC4Media

More from Leena N (20)

The last mile problemLeena N

Have you ever asked a programmer how much longer “this” is going to take? Here goes another typical answer. I am done with most of the tasks, need extra time to finish the last few ones. And the “last few tasks” never ends or takes enormous amounts of time. On the one hand, we all know that estimates always go wrong. But there is another aspect to this too, i.e. the last mile problem. It can be because of the “fear or shipping” or not applying the guideline “done is better than perfect”. This talk is about a few tricks I tried not to get into the “perfection” mode; instead, get into the habit of “shipping”. Surprisingly, that helped me to avoid providing estimates :)

Expand Contract Pattern for Continuous Delivery of DatabasesLeena N

This document discusses techniques for continuously delivering database changes, including database refactoring. It describes strategies like splitting tables and columns, adding transition periods, using versioning, automation with testing, and making changes incrementally and reversibly. Database refactoring includes structural, data quality, referential integrity, and transformation changes. Tools, strategies for low risk releases, and patterns like branch by abstraction and strangler are recommended to support evolutionary development and continuous delivery of database changes.

Sprinkle javascript using stimulus jsLeena N

n this world of Microservices, I am building a Monolith app. In this world of React and Vue, am building a server-side rendered app. However, I need Javascript. I can’t avoid that. I need some parts of the page updated dynamically. I need to show/hide certain parts of the page depending upon user actions. I don’t want JQuery for the obvious reasons. Slow.., Heavy and then, of course, it can easily create spaghetti code. That is when I came across Stimulus JS - a modest Javascript framework. It sprinkles Javascript to add behaviour to your HTML. It has a controller, action and targets (i.e. the HTML elements). Moreover, it pairs well with Turbolinks. So I don’t need to do the circus of converting JSON to DOM. I’ve been using Stimulus for over a year and its been quite good. This talk is about my experiences with Stimulus with a few examples. I will share recommendations on where it might be useful and where it is not.

Patterns and practices for evolvability - the key for technical agilityLeena N

Evolvability refers to the ability to adapt to market needs and the changing environment. Mainly two kinds of evolvability are needed: Product evolving as per the market needs to avoid Building something that nobody wants The architecture and the design of the software evolving to allow the team to make faster changes to the product without breaking things That is why it is crucial to build the right product and build it in the right way.

Expand contract pattern - Continuous Delivery for Databases - DevOpsDays SeattleLeena N

Modifying the schema of a production database is *hard*. If something goes wrong, the impact on both customers and the team can be enormous. And it can be hard or even impossible to rollback a database schema change if things go wrong. And the same is true for any architectural change for a production application. The Branch by Abstraction and Strangler Pattern makes significant application changes easier. Are there any similar patterns we can use to make production database changes less risky? Indeed, there are. The Expand/Contract pattern is a blueprint for making the database migration. It makes the remodelling both reversible and safe. By *expanding* the application to accommodate both the old and the new schemas in parallel, we can give ourselves time to: - Migrate any downstream dependencies on the old database schema - Gain confidence that the migration is safe We *contract* the application to the new version, once we’ve satisfied that the old schema is no longer needed. The pattern helps to make significant, but necessary refactorings to your data model in a **continuous delivery way**. Most importantly, without threatening the robustness of your production applications.

Expand contract pattern continuous delivery and databasesLeena N

Modifying the schema of a production database is hard. If something goes wrong, the impact on both customers and the team can be enormous. And it can be hard or even impossible to rollback a database schema change if things go wrong. And the same is true for any architectural change for a production application. The Branch by Abstraction and Strangler Pattern makes significant application changes easier. Are there any similar patterns we can use to make production database changes less risky? Indeed, there are. The Expand/Collapse pattern is a blueprint for making the database migration and makes the remodelling both reversible and safe. By expanding the application to accommodate both the old and the new schemas in parallel, we can give ourselves time to: - Migrate any downstream dependencies on the old database schema; - Gain confidence that the migration is safe. We contract the application to the new version, once we’ve satisfied that the old schema is no longer needed. The pattern helps to make significant, but necessary refactorings to your data model in a continuous delivery way. Most importantly, without threatening the robustness of your production applications.

Expand contract pattern - Continuous Delivery and DatabasesLeena N

Importance of Showing UpLeena N

GrowthLeena N

What does career growth mean? How does one grow in their career? How do you choose an organisation which allows one to grow? One grows when the environment allows growing. I am not talking about the std. the corporate ladder. One can climb those automatically as the time passes. But all of us agree that it doesn't mean "growth". The key ingredients for the actual growth is the following: * Purpose - the intention to contribute to the well-being of others * Practice - Consistent and deliberate practice * Perseverance - Persistence to try out hard things The talk is about examples and stories about these ingredients and what makes those who have these ingredients and those who don't.

TDD, Refactoring - WorkshopLeena N

This document discusses test-driven development (TDD) and refactoring using the Gilded Rose kata exercise. It provides rules for TDD, such as only writing production code with a failing test and refactoring code after each test. Simple design principles are outlined, like revealing intention and avoiding duplication. Extreme object-oriented programming rules are also listed, like limiting indentation and properties. The goal is to practice TDD and refactoring skills through the Gilded Rose kata.

Technical debt a catch all phrase--Leena N

Developing, building, testing and deploying react native appsLeena N

Continuous delivery from the trenchesLeena N

This document discusses two companies' journeys to continuous delivery of software. The first story describes automating a loan processing platform that now processes close to $4 million in loans with a small team. The second story automated a mobile device management solution for healthcare. The document then outlines the continuous delivery process used, including practices like continuous integration, deployment pipelines and emphasizing delivering business value. Challenges discussed include balancing speed and quality while improving processes through retrospectives.

Introduction to continuous deliveryLeena N

Continuous delivery is a software development practice where software can be released to production at any time by building software in a way that enables frequent, automated releases. It involves practices like continuous integration, where code is automatically merged and tested frequently, automated testing and deployment, and using deployment pipelines and tools to streamline the release process. Many large tech companies practice continuous delivery, with some deploying new code in minutes or every 11 seconds to get changes to users quickly.

Merge hells - Feature Toggles to the rescueLeena N

The document discusses how feature toggles can help address "merge hells" that can occur with continuous integration. Feature toggles allow incomplete features to be deployed without being released, avoiding the need to rollback deployments. They enable options like A/B testing, canary releasing, and managing experimental and operations toggles. To manage feature toggles, teams should follow mainline development practices, use feature toggle tools, set expiry dates for toggles, and consider toggles as a first step towards continuous delivery.

Deliver with impactLeena N

This document discusses impact mapping as a technique for delivering projects with impact. It provides an example of impact mapping for an MDM (mobile device management) product. The key steps of impact mapping include: defining goals and who they impact; identifying desired behaviors and how to enable them; establishing metrics to measure impact; and planning milestones to test assumptions. Impact mapping focuses on creating actual behavioral change rather than just shipping software.

Learnings while building Mobile Device Management [MDM] Leena N

Javascript Testing Tools - OverviewLeena N

This document discusses different types of testing tools, including unit testing tools like Jasmine and Mocha that allow for quick feedback during test-driven development, end-to-end testing tools like Selenium and Protractor that simulate user interactions, contract testing tools like Pact that test design contracts, and screenshot comparison tools like Wraith and Resemble.js for visual regression testing. It also mentions that unit tests should have high value but low maintenance, end-to-end tests have high effort for maintenance, and that testing strategies should follow the testing pyramid with more unit and integration tests than end-to-end tests.

Continuous delivery using jenkinsLeena N

This document discusses the importance of continuous delivery using Jenkins. It introduces continuous integration and continuous delivery, explaining that continuous integration provides fast feedback on code changes while continuous delivery provides feedback on production readiness. It outlines how to set up a build pipeline in Jenkins to guarantee production readiness and make releases risk-free and automated. The document emphasizes that continuous delivery satisfies customers through early and frequent delivery of software and encourages teams to take responsibility for releases through continuous improvement.

Culture of Continuous DeliveryLeena N

This document discusses the culture of continuous delivery. It promotes building quality in from the start, keeping the build always deployable, and continuous improvement. Continuous delivery aspects include automating the build, having a deployable build, continuous integration, build pipelines, configuration management, release management, and using Kanban and feature toggles. Practicing continuous delivery leads to a great culture with values like delighted customers and software craftsmanship. It also discusses concepts from neuroscience like how the brain reacts to stress and rewards that relate to continuous delivery practices.

The last mile problemLeena N

Expand Contract Pattern for Continuous Delivery of DatabasesLeena N

Sprinkle javascript using stimulus jsLeena N

Patterns and practices for evolvability - the key for technical agilityLeena N

Expand contract pattern - Continuous Delivery for Databases - DevOpsDays SeattleLeena N

Expand contract pattern continuous delivery and databasesLeena N

Expand contract pattern - Continuous Delivery and DatabasesLeena N

Importance of Showing UpLeena N

GrowthLeena N

TDD, Refactoring - WorkshopLeena N

Technical debt a catch all phrase--Leena N

Developing, building, testing and deploying react native appsLeena N

Continuous delivery from the trenchesLeena N

Introduction to continuous deliveryLeena N

Merge hells - Feature Toggles to the rescueLeena N

Deliver with impactLeena N

Learnings while building Mobile Device Management [MDM] Leena N

Javascript Testing Tools - OverviewLeena N

Continuous delivery using jenkinsLeena N

Culture of Continuous DeliveryLeena N

Recently uploaded (20)

Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep DiveScyllaDB

Want to learn practical tips for designing systems that can scale efficiently without compromising speed? Join us for a workshop where we’ll address these challenges head-on and explore how to architect low-latency systems using Rust. During this free interactive workshop oriented for developers, engineers, and architects, we’ll cover how Rust’s unique language features and the Tokio async runtime enable high-performance application development. As you explore key principles of designing low-latency systems with Rust, you will learn how to: - Create and compile a real-world app with Rust - Connect the application to ScyllaDB (NoSQL data store) - Negotiate tradeoffs related to data modeling and querying - Manage and monitor the database for consistently low latencies

#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025BookNet Canada

Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next. Link to recording, transcript, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/ Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.

IEDM 2024 Tutorial2_Advances in CMOS Technologies and Future Directions for C...organizerofv

Manifest Pre-Seed Update | A Humanoid OEM Deeptech In Francechb3

Role of Data Annotation Services in AI-Powered ManufacturingAndrew Leo

SAP Modernization: Maximizing the Value of Your SAP S/4HANA Migration.pdfPrecisely

Build Your Own Copilot & Agents For DevsBrian McKeiver

Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan

This is a Quick Research Guide (QRG). QRGs include the following: - A brief, high-level overview of the QRG topic. - A milestone timeline for the QRG topic. - Links to various free online resource materials to provide a deeper dive into the QRG topic. - Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic. QRGs planned for the series: - Artificial Intelligence QRG - Quantum Computing QRG - Big Data Analytics QRG - Spacecraft Guidance, Navigation & Control QRG (coming 2026) - UK Home Computing & The Birth of ARM QRG (coming 2027) Any questions or comments? - Please contact Arthur Morgan at [email protected]. 100% human made.

AI EngineHost Review: Revolutionary USA Datacenter-Based Hosting with NVIDIA ...SOFTTECHHUB

I started my online journey with several hosting services before stumbling upon Ai EngineHost. At first, the idea of paying one fee and getting lifetime access seemed too good to pass up. The platform is built on reliable US-based servers, ensuring your projects run at high speeds and remain safe. Let me take you step by step through its benefits and features as I explain why this hosting solution is a perfect fit for digital entrepreneurs.

Linux Professional Institute LPIC-1 Exam.pdfRHCSA Guru

Transcript: #StandardsGoals for 2025: Standards & certification roundup - Tec...BookNet Canada

Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next. Link to recording, presentation slides, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/ Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.

Greenhouse_Monitoring_Presentation.pptx.hpbmnnxrvb

Splunk Security Update | Public Sector Summit Germany 2025Splunk

Cybersecurity Identity and Access Solutions using Azure ADVICTOR MAESTRE RAMIREZ

TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc

Most consumers believe they’re making informed decisions about their personal data—adjusting privacy settings, blocking trackers, and opting out where they can. However, our new research reveals that while awareness is high, taking meaningful action is still lacking. On the corporate side, many organizations report strong policies for managing third-party data and consumer consent yet fall short when it comes to consistency, accountability and transparency. This session will explore the research findings from TrustArc’s Privacy Pulse Survey, examining consumer attitudes toward personal data collection and practical suggestions for corporate practices around purchasing third-party data. Attendees will learn: - Consumer awareness around data brokers and what consumers are doing to limit data collection - How businesses assess third-party vendors and their consent management operations - Where business preparedness needs improvement - What these trends mean for the future of privacy governance and public trust This discussion is essential for privacy, risk, and compliance professionals who want to ground their strategies in current data and prepare for what’s next in the privacy landscape.

DevOpsDays Atlanta 2025 - Building 10x Development Organizations.pptxJustin Reock

Building 10x Organizations with Modern Productivity Metrics 10x developers may be a myth, but 10x organizations are very real, as proven by the influential study performed in the 1980s, ‘The Coding War Games.’ Right now, here in early 2025, we seem to be experiencing YAPP (Yet Another Productivity Philosophy), and that philosophy is converging on developer experience. It seems that with every new method we invent for the delivery of products, whether physical or virtual, we reinvent productivity philosophies to go alongside them. But which of these approaches actually work? DORA? SPACE? DevEx? What should we invest in and create urgency behind today, so that we don’t find ourselves having the same discussion again in a decade?

UiPath Community Berlin: Orchestrator API, Swagger, and Test Manager APIUiPathCommunity

Join this UiPath Community Berlin meetup to explore the Orchestrator API, Swagger interface, and the Test Manager API. Learn how to leverage these tools to streamline automation, enhance testing, and integrate more efficiently with UiPath. Perfect for developers, testers, and automation enthusiasts! 📕 Agenda Welcome & Introductions Orchestrator API Overview Exploring the Swagger Interface Test Manager API Highlights Streamlining Automation & Testing with APIs (Demo) Q&A and Open Discussion Perfect for developers, testers, and automation enthusiasts! 👉 Join our UiPath Community Berlin chapter: https://community.uipath.com/berlin/ This session streamed live on April 29, 2025, 18:00 CET. Check out all our upcoming UiPath Community sessions at https://community.uipath.com/events/.

Mobile App Development Company in Saudi ArabiaSteve Jonas

EmizenTech is a globally recognized software development company, proudly serving businesses since 2013. With over 11+ years of industry experience and a team of 200+ skilled professionals, we have successfully delivered 1200+ projects across various sectors. As a leading Mobile App Development Company In Saudi Arabia we offer end-to-end solutions for iOS, Android, and cross-platform applications. Our apps are known for their user-friendly interfaces, scalability, high performance, and strong security features. We tailor each mobile application to meet the unique needs of different industries, ensuring a seamless user experience. EmizenTech is committed to turning your vision into a powerful digital product that drives growth, innovation, and long-term success in the competitive mobile landscape of Saudi Arabia.

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

Electronic_Mail_Attacks-1-35.pdf by xploitniftliyevhuseyn

Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep DiveScyllaDB

#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025BookNet Canada

IEDM 2024 Tutorial2_Advances in CMOS Technologies and Future Directions for C...organizerofv

Manifest Pre-Seed Update | A Humanoid OEM Deeptech In Francechb3

Role of Data Annotation Services in AI-Powered ManufacturingAndrew Leo

SAP Modernization: Maximizing the Value of Your SAP S/4HANA Migration.pdfPrecisely

Build Your Own Copilot & Agents For DevsBrian McKeiver

Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan

AI EngineHost Review: Revolutionary USA Datacenter-Based Hosting with NVIDIA ...SOFTTECHHUB

Linux Professional Institute LPIC-1 Exam.pdfRHCSA Guru

Transcript: #StandardsGoals for 2025: Standards & certification roundup - Tec...BookNet Canada

Greenhouse_Monitoring_Presentation.pptx.hpbmnnxrvb

Splunk Security Update | Public Sector Summit Germany 2025Splunk

Cybersecurity Identity and Access Solutions using Azure ADVICTOR MAESTRE RAMIREZ

TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc

DevOpsDays Atlanta 2025 - Building 10x Development Organizations.pptxJustin Reock

UiPath Community Berlin: Orchestrator API, Swagger, and Test Manager APIUiPathCommunity

Mobile App Development Company in Saudi ArabiaSteve Jonas

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

Electronic_Mail_Attacks-1-35.pdf by xploitniftliyevhuseyn

Continuous delivery for Android

1. Continuous Delivery for Android By @leenasn

3. Agenda ● Why Continuous Delivery ● Continuous Delivery for Android Apps - Challenges ● Overview of the Tools

8. Building something nobody wants is the ultimate form of waste ~Eric Ries The Lean Startup

9. Think about how long would it take you to deliver a change of one line of code within your application to production ~Mary and Tom Poppendieck Lean Software Development, An Agile Toolkit

12. https://www.infoq.com/articles/standish-chaos-2015

14. Continuous Delivery “Continuous Delivery is a software development discipline where you build software in such a way that the software can be released to production at any time.” http://martinfowler.com/bliki/ContinuousDelivery.html

15. Continuous Integration “Continuous integration (CI) is the practice, in software engineering, of merging all developer working copies to a shared mainline several times a day.”

16. Mainline Development

17. Feature Toggles

18. Automated Testing

19. Automated Deployment

20. Deployment Pipeline

21. CD vs CD

23. CD for Android Challenges

24. Not much Control

25. The Next Web

26. Slow Unit tests

27. Solutions ???

28. https://twitter.com/mobileapptimize/status/713441244639281154

29. Playstore Alpha/Beta Testing

32. Testing Tools

38. Build Tools

43. Static Analysis Tools

45. Summary

46. Done = Released

47. Work in small batches

49. http://cnmnewz.com/wp-content/uploads/2014/06/Golden-Gate-Bridge-with-Net-AP.jpg

50. Case Studies http://mobiledeliverydays.org/program/

51. https://github.com/multunus/android-sample-app

52. References

53. 1. http://martinfowler.com/articles/feature-toggles.html 2. http://www.multunus.com/blog/2016/03/merge-hells-feature-toggles-resc ue/ 3. http://www.slideshare.net/TimothyFitz/continuous-deployment-beyond-c ontinuous-delivery 4. http://blog.crisp.se/2013/02/05/yassalsundman/continuous-delivery-vs-co ntinuous-deployment 5. https://gradle.org/case-study-continuous-delivery-netflix/ 6. http://mobiledeliverydays.org/program/ References

54. Leena S N @leenasn / [email protected]

Continuous delivery for Android

Recommended

More Related Content

What's hot (20)

Similar to Continuous delivery for Android (20)

More from Leena N (20)

Recently uploaded (20)

Continuous delivery for Android