Mobile Apps CI
•
1 like•176 views
This document discusses continuous integration and delivery for mobile apps. It covers Git workflows like centralized, feature branching, and Gitflow models. It also discusses Fastlane for automating building, testing, and releasing mobile apps. Fastlane tools like deliver, snapshot, and sigh are mentioned. Jenkins is presented as an automation server that supports a wide range of plugins. The document concludes with a promise to demonstrate how easy CI/CD can be set up.
Report
Share
Report
Share
Download to read offline
Recommended
To the App Store in One Month
The document outlines steps for releasing an app to the app store within one month. It recommends setting aside two weeks for development and 40 hours to build the app quickly. It suggests focusing on features first and testing later. The document provides tips on tooling, testing, accessibility, and sharing the project code. Key frameworks and extensions like WatchKit, Firebase, and Fastlane tools are mentioned to help streamline the process.
SanDiego_DevOps_Meetup_9212016-v8
Mitchell International has been providing property and casualty claims services for 70 years. Raj Makkar and Richard Fong discuss Mitchell's journey to continuous integration and delivery over the past 7 years. They moved from a slow "big build" process controlled by one team to a componentized approach where developers control builds. Today, builds occur on every check-in with immediate feedback. They use tools like Jenkins and Artifactory to manage over 1400 jobs per day across many platforms. Their goal is rapid, quality software delivery through a culture of automation, testing, and collaboration across teams.
Mobile DevOps with VSTS and AppCenter
This document discusses using DevOps tools like Visual Studio Team Services and App Center for mobile app development. It provides an overview of how they can be used for source control, continuous integration, testing, and releasing mobile apps to internal and external distribution channels. Key capabilities covered include building apps for different environments and configurations, running automated UI tests on real devices, and releasing apps to testers or production through App Center or Google Play.
Google IO 2017 Recap
A recap of the important developer announcements @Google IO 2017 - focusing on Android instant apps, Google play app signing and Firebase
Salesforce World Tour 2016 : Lightning Out : Components on any Platform
This document summarizes a presentation about using Lightning components on any platform. It discusses how Lightning components work, how to enable them in Lightning Experience and the Lightning App Builder. It also introduces Lightning Out, which allows components to be used outside of Lightning Experience, such as in Google Docs using Google App Scripts. Requirements for Lightning Out include making components global and using a Lightning dependency app. The document provides demos of integrating Lightning components into Google Docs to search for addresses.
Scalable APIs with Azure Functions
Christos Matskas discusses Azure Functions, a serverless computing service that allows developers to run code without managing infrastructure. Azure Functions provides benefits like reduced DevOps workload and faster time to market by managing applications rather than servers. It uses a variety of triggers and bindings to connect events to code execution and integrates with tools for local development, monitoring, and deployment.
Continuous delivery @ iyzico
This document discusses iyzico's continuous delivery practices. Iyzico is a fintech company focused on payments with 62 employees, including 25-30 in engineering. They use 1 week sprints with cross-functional teams and fullstack engineers. Their continuous delivery process includes nightly builds, testing, deployment to dev environments, monitoring, and feedback reporting. The phases include building artifacts, deployment, and monitoring after deployment. They aim to satisfy customers through early and continuous delivery of valuable software.
Postman Webinar: How Ping Identity Uses Postman across the API Lifecycle
Jason Hatchett, Anthony Dombrowski, and Gideon McKee from Ping Identity and Joyce Lin from Postman discuss Ping’s journey with Postman. This journey started with QA testing and ultimately grew to enabling efficient collaboration throughout the API lifecycle from development to customer onboarding and documentation.
Recommended
To the App Store in One Month
The document outlines steps for releasing an app to the app store within one month. It recommends setting aside two weeks for development and 40 hours to build the app quickly. It suggests focusing on features first and testing later. The document provides tips on tooling, testing, accessibility, and sharing the project code. Key frameworks and extensions like WatchKit, Firebase, and Fastlane tools are mentioned to help streamline the process.
SanDiego_DevOps_Meetup_9212016-v8
Mitchell International has been providing property and casualty claims services for 70 years. Raj Makkar and Richard Fong discuss Mitchell's journey to continuous integration and delivery over the past 7 years. They moved from a slow "big build" process controlled by one team to a componentized approach where developers control builds. Today, builds occur on every check-in with immediate feedback. They use tools like Jenkins and Artifactory to manage over 1400 jobs per day across many platforms. Their goal is rapid, quality software delivery through a culture of automation, testing, and collaboration across teams.
Mobile DevOps with VSTS and AppCenter
This document discusses using DevOps tools like Visual Studio Team Services and App Center for mobile app development. It provides an overview of how they can be used for source control, continuous integration, testing, and releasing mobile apps to internal and external distribution channels. Key capabilities covered include building apps for different environments and configurations, running automated UI tests on real devices, and releasing apps to testers or production through App Center or Google Play.
Google IO 2017 Recap
A recap of the important developer announcements @Google IO 2017 - focusing on Android instant apps, Google play app signing and Firebase
Salesforce World Tour 2016 : Lightning Out : Components on any Platform
This document summarizes a presentation about using Lightning components on any platform. It discusses how Lightning components work, how to enable them in Lightning Experience and the Lightning App Builder. It also introduces Lightning Out, which allows components to be used outside of Lightning Experience, such as in Google Docs using Google App Scripts. Requirements for Lightning Out include making components global and using a Lightning dependency app. The document provides demos of integrating Lightning components into Google Docs to search for addresses.
Scalable APIs with Azure Functions
Christos Matskas discusses Azure Functions, a serverless computing service that allows developers to run code without managing infrastructure. Azure Functions provides benefits like reduced DevOps workload and faster time to market by managing applications rather than servers. It uses a variety of triggers and bindings to connect events to code execution and integrates with tools for local development, monitoring, and deployment.
Continuous delivery @ iyzico
This document discusses iyzico's continuous delivery practices. Iyzico is a fintech company focused on payments with 62 employees, including 25-30 in engineering. They use 1 week sprints with cross-functional teams and fullstack engineers. Their continuous delivery process includes nightly builds, testing, deployment to dev environments, monitoring, and feedback reporting. The phases include building artifacts, deployment, and monitoring after deployment. They aim to satisfy customers through early and continuous delivery of valuable software.
Postman Webinar: How Ping Identity Uses Postman across the API Lifecycle
Jason Hatchett, Anthony Dombrowski, and Gideon McKee from Ping Identity and Joyce Lin from Postman discuss Ping’s journey with Postman. This journey started with QA testing and ultimately grew to enabling efficient collaboration throughout the API lifecycle from development to customer onboarding and documentation.
Twelve factor apps
The twelve-factor app methodology advocates for building software-as-a-service apps that are portable, scalable and suitable for deployment on modern cloud platforms. It consists of twelve factors including storing code in revision control, declaring and isolating dependencies, storing configs in environment variables, treating backing services as attached resources, separating build and run stages, executing processes as stateless and share-nothing, exporting via port binding, scaling out via processes, maximizing robustness through fast startup and graceful shutdown, keeping development and production parity, treating logs as event streams, and running one-off admin/management tasks as processes. The methodology aims to minimize divergence between development and production for continuous deployment.
BDD with Behat Selenium, Sahi and Sauce
This talk given at London Tester Gathering on 12 Jan at Agile testing meetup. http://www.meetup.com/agiletesting/events/46428972/. This talk was about using Behat for web acceptance testing with selenium, sahi driver and Sauce Labs.
CICD by Teerapat
This document discusses continuous integration and continuous delivery (CI/CD) practices. It explains that CI/CD involves automating the build, testing, and deployment process through the use of a single source repository, build automation, and self-testing to find and address problems quickly. The goal is to continuously deliver high quality software to production by building, testing, and releasing software frequently in a automated way.
Anatomy of a Continuous Integration and Delivery (CICD) Pipeline
This presentation covers the anatomy of a production CICD pipeline that is used to develop and deploy the cancer research application Oncoscape (https://oncoscape.sttrcancer.org)
Automating Hybrid Applications with Appium
When creating a mobile application, organisations have a few options to choose from; mobile web, native or a hybrid application. Where web apps are just websites that can be accessed on the internet via a mobile browser like Chrome or Safari, native apps are applications that are developed for a specific platform such as Android or iOS. Hybrid apps are different because they possess elements from native apps and web apps.
When automating web applications, Selenium commands are used. Nine out of ten times the same automation script can be used for mobile web applications as our desktop web applications. With native apps however, we need to look deeper into the differences between Android and iOS apps before we can use Appium commands.
But how should you automate hybrid apps, can or do you need to choose one of the two automation strategies or is there also a hybrid approach for automating hybrid apps?
That’s what we are going to talk about during this webinar. We will be looking into how to detect a hybrid application for Android and iOS, the do’s and the don’ts when it comes to automating a hybrid application and we will provide you with tips and tricks on how to make this work for both Android and iOS.
By the end of this webinar, you’ll be able to create your own Appium scripts to automate Android and iOS hybrid mobile applications.
Key Takeaways:
- Understand what a hybrid mobile application is
- How to detect a hybrid mobile application
- Learn how iOS and Android handle hybrid mobile applications
- Learn how to automate hybrid mobile applications
Why You Need a Developer Relations Team for Your API
Developer Relations teams focus on three key areas: 1) improving the developer experience through SDKs, documentation, demo apps and support, 2) building a developer community through events, conferences and an online community, and 3) collecting feedback across multiple channels to understand developers and improve the API. Having a DevRel team leads to a happier developer community, easier onboarding, more successful customers, and making the API a leader in its market.
Agile Fundamental Skill Set
This document provides an introduction to agile programmer skills. It will cover agile fundamental skill sets over 90 minutes, including recommendations for books to read and a demonstration of test-driven development (TDD). Attendees will work in teams to discuss important agile skills, write down their ideas, and share with others. The presentation will also cover mandatory skills for agile programmers, principles behind the agile manifesto, risks in traditional vs. agile development, the cost of change curve, agile development processes like scrum, and key knowledge areas including designing & programming with TDD and refactoring, testing, team behaviors, structuring work, and environment.
Webrazzi online code: iyzico continuous delivery
webrazzi online: code canlı yayınında bahsettiğim iyzico, engineering ekibi, tech stack ve continuous delivery / devops başlıkları
Enterprise E-commerce Webinar Series, Episode 2: Deploying and Monitoring You...
Note: This webinar is the second in Postman's three-part webinar series on implementing an API-first strategy in enterprise e-commerce. The series, hosted by Postman Chief Evangelist Kin Lane, will walk you through key topics and how-to content via a hypothetical e-commerce enterprise, Union Fashion (see it on GitHub).
Continuing with our series, the second webinar will dive into actually deploying and monitoring an API using the Postman platform. We will take the API we developed as part of our previous API-first webinar, and actually bring it to life by focusing on the following areas:
- Versions
- Monitors
- Mocks
- Environment
- Documentation
- Feedback Loops
The full video for this session can be found at: https://www.youtube.com/watch?v=jO2M_kqb-jo&t=1659s
Top10 Characteristics of Awesome Apps
In this talk, you will hear the best practices from analysts at Gartner, engineers at Heroku, and experiences at VSP distilled down into a top ten list of characteristics that applications ought to have to achieve high availability, scalability and flexibility. Target audience includes developers of APIs and web-based applications, the analysts and architects that design them and the infrastructure teams that support them.
Creating reusable pieces in Logic Apps
This document discusses reusable pieces in Logic Apps and Azure Functions integration. It announces an upcoming Integration Monday webinar on using BizTalk with Logic Apps and Azure Functions. The presenter then demonstrates how to easily create reusable logic app workflows by calling nested logic apps from within the designer. Users are encouraged to provide feedback and suggestions to help improve Logic Apps.
Advanced Spring Boot with Consul
Modern software development faces challenges around smaller teams, changing technologies, and platform agility. This document discusses using Consul for service discovery and configuration with Spring Boot applications. It provides an example of a basic Spring Boot invoice and tax service, and how Consul allows the services to dynamically discover and register each other without needing to know configuration details. The document demonstrates the advantages of Consul and Spring Boot including monitoring, deployment flexibility, and separation of environments. It provides instructions for setting up a local Consul development environment and links to example code and documentation.
Azure Integration DTAP Series, How to go from Development to Production – Par...
A series of sessions on how to set up a Build & Release setup for Common integration parts with VSTS with hands on and understanding the common tasks.
Continuous Integration with Bamboo for Salesforce
This document discusses using Bamboo for continuous integration in Salesforce development. Bamboo is a continuous integration server from Atlassian that supports builds in many languages using tools like Ant and Maven. It can deploy Salesforce metadata and code using the Force.com Migration Tool. A Bamboo build defines a deployment process through plans, jobs, tasks and variables to deploy changes from a repository on a scheduled or triggered basis, while tracking deployments, permissions, and notifications. Considerations for using Bamboo include project size and type, limitations on deployable components, and occasional dependency issues.
QConSP 2014 - Continuous Delivery - Part 03 - Continuous Integration
The document discusses principles of continuous integration including version control, automation, and testing. It describes a basic continuous integration/continuous delivery (CI/CD) pipeline with stages for committing code, compiling, testing, and deploying to environments like acceptance, capacity, and production. Jenkins is presented as a tool for implementing CI/CD pipelines through automated jobs that can pull code, build, test, analyze, and deploy software.
Logic apps and PowerApps - Integrate across your APIs
We have a number of new feature in Logic apps and PowerApps that make it easier than ever to build workflows that orchetstrate across any RESTful API. We will cover some of the latest updates to Logic apps and PowerApps.
Versioning strategy for a complex internal API (Konstantin Yakushev)
This is a session given by Konstantin Yakushev at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
API versioning is a very heated topic in API design world. Common approaches are passing version number explicitly (with a lot of fairly useless discussion on where exactly to put that number) or only introducing backwards-compatible changes.
When creating internal API for Badoo applications we found those approaches to be too limiting. Passing version number requires implementers to accommodate for all breaking changes when bumping version – even when it’s not required for business goals of that application at the time. Instead of driving value for business, application developers are in constant race to keep up with the API.
Never introducing incompatible changes is also not an option. After several feature redesigns (something that may happen at Badoo once every few weeks) protocol becomes bloated and half of the fields transmitted over the wire start being useless.
This talk is about our approach to versioning as part of client-server component negotiation. Client announces features and capabilities it supports and server replies with features status: whether they are enabled or disabled and whether they can be enabled by some user action (e. g. by buying some paid product).
Beside those componentized features, client also sends support flags such as SUPPORT_IMAGE_SIZE_VIA_URL which affects how API works. We use those flags where in typical API a version number bump would be required.
This approach allows both server and client to understand their current state and adjust their code accordingly – essentially, a tailor-made API for every client. Gathering data on feature and flag support among clients allows us to remove old code branches while continuing to evolve the API.
As a result, we are not afraid to change something when that change is required. Old clients continue to work while protocol rot is kept at low level.
In this talk I will give details on how exactly this versioning scheme work, how we test those changes, how and when we deprecate our old clients and note some stats and insights from using this scheme at Badoo for several years.
Automating the API Product Lifecycle
Looking at the full API Product Lifecycle, from defining an API and implementing the API, to launching with a solid developer site and experience, let’s see the newest tools - and potentially upcoming opportunities - to automate the creation of a solid developer experience.
Creating a successful API requires a proper process from concept and design, through development, and into ongoing maintenance and responsive developer support. As developer expectations for better-quality APIs increase, tools have made it easier to implement this well. Thanks to standards like OpenAPIs, it’s easier to create a quality API, developer site, and overall experience. Many of us create API documentation or code libraries automatically from an OpenAPI spec, but there’s a lot more coming along to make our lives easier, and to make our APIs look better. In reviewing the full API Product Lifecycle to design an API people will use, let’s see the newest tools - and potentially upcoming opportunities - to better automate the creation of a compelling developer program.
Continuous Delivery: Fly the Friendly CI in Pivotal Cloud Foundry with Concourse
This document provides an overview of continuous integration (CI) and continuous delivery (CD) using Concourse. It introduces Concourse and discusses why containers and pipelines are useful for CI/CD. It then demonstrates how to use Concourse in practice with examples and explains how to get started using Concourse for CI/CD workflows. The key aspects covered are Concourse's simple and scalable pipeline model using resources, tasks, and jobs, how containerization provides dependable and isolated executions, and how pipelines allow flexible yet efficient software testing and deployment.
Continuous Integration
Continuous integration involves integrating code changes frequently - usually multiple times per day - by having an automated build and test process. This helps reduce integration problems and leads to more cohesive software. Best practices include having a single source repository, automated builds and tests, fixing broken builds immediately, and keeping the build process fast. The document then provides examples of continuous integration pipelines at Alea using tools like Docker, Jenkins, and custom scripts to build and test Python and Golang components and libraries. It emphasizes automating everything and following best practices to implement continuous integration effectively.
03 02 - tizen app development with visual studio mobile center and team services
The reference process of Tizen app development on the base of Tizen-compatible life cycle and continuous integration services, provided by Microsoft Visual Studio in partnership with Samsung.
The Mobile Center Tizen SDK offers device side API for collecting app running time statistics and observing it on the Mobile Center Web UI.
The Team Services supply build task queue, which automatically builds, signs and deploys Tizen app right after the app sources are submitted to the online repository.
DevOps & DevEx
DevEx aims to improve the developer experience by focusing on tooling, technologies, and documentation within a DevOps environment. This includes adopting integrated toolchains that streamline the development lifecycle through automation and by ensuring tools are well-tested, configurable, and have comprehensive documentation. The goal of DevEx is to create an optimal software production environment by minimizing friction between development, testing, and operations teams through collaboration, shared tools, and improved processes.
More Related Content
What's hot
Twelve factor apps
The twelve-factor app methodology advocates for building software-as-a-service apps that are portable, scalable and suitable for deployment on modern cloud platforms. It consists of twelve factors including storing code in revision control, declaring and isolating dependencies, storing configs in environment variables, treating backing services as attached resources, separating build and run stages, executing processes as stateless and share-nothing, exporting via port binding, scaling out via processes, maximizing robustness through fast startup and graceful shutdown, keeping development and production parity, treating logs as event streams, and running one-off admin/management tasks as processes. The methodology aims to minimize divergence between development and production for continuous deployment.
BDD with Behat Selenium, Sahi and Sauce
This talk given at London Tester Gathering on 12 Jan at Agile testing meetup. http://www.meetup.com/agiletesting/events/46428972/. This talk was about using Behat for web acceptance testing with selenium, sahi driver and Sauce Labs.
CICD by Teerapat
This document discusses continuous integration and continuous delivery (CI/CD) practices. It explains that CI/CD involves automating the build, testing, and deployment process through the use of a single source repository, build automation, and self-testing to find and address problems quickly. The goal is to continuously deliver high quality software to production by building, testing, and releasing software frequently in a automated way.
Anatomy of a Continuous Integration and Delivery (CICD) Pipeline
This presentation covers the anatomy of a production CICD pipeline that is used to develop and deploy the cancer research application Oncoscape (https://oncoscape.sttrcancer.org)
Automating Hybrid Applications with Appium
When creating a mobile application, organisations have a few options to choose from; mobile web, native or a hybrid application. Where web apps are just websites that can be accessed on the internet via a mobile browser like Chrome or Safari, native apps are applications that are developed for a specific platform such as Android or iOS. Hybrid apps are different because they possess elements from native apps and web apps.
When automating web applications, Selenium commands are used. Nine out of ten times the same automation script can be used for mobile web applications as our desktop web applications. With native apps however, we need to look deeper into the differences between Android and iOS apps before we can use Appium commands.
But how should you automate hybrid apps, can or do you need to choose one of the two automation strategies or is there also a hybrid approach for automating hybrid apps?
That’s what we are going to talk about during this webinar. We will be looking into how to detect a hybrid application for Android and iOS, the do’s and the don’ts when it comes to automating a hybrid application and we will provide you with tips and tricks on how to make this work for both Android and iOS.
By the end of this webinar, you’ll be able to create your own Appium scripts to automate Android and iOS hybrid mobile applications.
Key Takeaways:
- Understand what a hybrid mobile application is
- How to detect a hybrid mobile application
- Learn how iOS and Android handle hybrid mobile applications
- Learn how to automate hybrid mobile applications
Why You Need a Developer Relations Team for Your API
Developer Relations teams focus on three key areas: 1) improving the developer experience through SDKs, documentation, demo apps and support, 2) building a developer community through events, conferences and an online community, and 3) collecting feedback across multiple channels to understand developers and improve the API. Having a DevRel team leads to a happier developer community, easier onboarding, more successful customers, and making the API a leader in its market.
Agile Fundamental Skill Set
This document provides an introduction to agile programmer skills. It will cover agile fundamental skill sets over 90 minutes, including recommendations for books to read and a demonstration of test-driven development (TDD). Attendees will work in teams to discuss important agile skills, write down their ideas, and share with others. The presentation will also cover mandatory skills for agile programmers, principles behind the agile manifesto, risks in traditional vs. agile development, the cost of change curve, agile development processes like scrum, and key knowledge areas including designing & programming with TDD and refactoring, testing, team behaviors, structuring work, and environment.
Webrazzi online code: iyzico continuous delivery
webrazzi online: code canlı yayınında bahsettiğim iyzico, engineering ekibi, tech stack ve continuous delivery / devops başlıkları
Enterprise E-commerce Webinar Series, Episode 2: Deploying and Monitoring You...
Note: This webinar is the second in Postman's three-part webinar series on implementing an API-first strategy in enterprise e-commerce. The series, hosted by Postman Chief Evangelist Kin Lane, will walk you through key topics and how-to content via a hypothetical e-commerce enterprise, Union Fashion (see it on GitHub).
Continuing with our series, the second webinar will dive into actually deploying and monitoring an API using the Postman platform. We will take the API we developed as part of our previous API-first webinar, and actually bring it to life by focusing on the following areas:
- Versions
- Monitors
- Mocks
- Environment
- Documentation
- Feedback Loops
The full video for this session can be found at: https://www.youtube.com/watch?v=jO2M_kqb-jo&t=1659s
Top10 Characteristics of Awesome Apps
In this talk, you will hear the best practices from analysts at Gartner, engineers at Heroku, and experiences at VSP distilled down into a top ten list of characteristics that applications ought to have to achieve high availability, scalability and flexibility. Target audience includes developers of APIs and web-based applications, the analysts and architects that design them and the infrastructure teams that support them.
Creating reusable pieces in Logic Apps
This document discusses reusable pieces in Logic Apps and Azure Functions integration. It announces an upcoming Integration Monday webinar on using BizTalk with Logic Apps and Azure Functions. The presenter then demonstrates how to easily create reusable logic app workflows by calling nested logic apps from within the designer. Users are encouraged to provide feedback and suggestions to help improve Logic Apps.
Advanced Spring Boot with Consul
Modern software development faces challenges around smaller teams, changing technologies, and platform agility. This document discusses using Consul for service discovery and configuration with Spring Boot applications. It provides an example of a basic Spring Boot invoice and tax service, and how Consul allows the services to dynamically discover and register each other without needing to know configuration details. The document demonstrates the advantages of Consul and Spring Boot including monitoring, deployment flexibility, and separation of environments. It provides instructions for setting up a local Consul development environment and links to example code and documentation.
Azure Integration DTAP Series, How to go from Development to Production – Par...
A series of sessions on how to set up a Build & Release setup for Common integration parts with VSTS with hands on and understanding the common tasks.
Continuous Integration with Bamboo for Salesforce
This document discusses using Bamboo for continuous integration in Salesforce development. Bamboo is a continuous integration server from Atlassian that supports builds in many languages using tools like Ant and Maven. It can deploy Salesforce metadata and code using the Force.com Migration Tool. A Bamboo build defines a deployment process through plans, jobs, tasks and variables to deploy changes from a repository on a scheduled or triggered basis, while tracking deployments, permissions, and notifications. Considerations for using Bamboo include project size and type, limitations on deployable components, and occasional dependency issues.
QConSP 2014 - Continuous Delivery - Part 03 - Continuous Integration
The document discusses principles of continuous integration including version control, automation, and testing. It describes a basic continuous integration/continuous delivery (CI/CD) pipeline with stages for committing code, compiling, testing, and deploying to environments like acceptance, capacity, and production. Jenkins is presented as a tool for implementing CI/CD pipelines through automated jobs that can pull code, build, test, analyze, and deploy software.
Logic apps and PowerApps - Integrate across your APIs
We have a number of new feature in Logic apps and PowerApps that make it easier than ever to build workflows that orchetstrate across any RESTful API. We will cover some of the latest updates to Logic apps and PowerApps.
Versioning strategy for a complex internal API (Konstantin Yakushev)
This is a session given by Konstantin Yakushev at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
API versioning is a very heated topic in API design world. Common approaches are passing version number explicitly (with a lot of fairly useless discussion on where exactly to put that number) or only introducing backwards-compatible changes.
When creating internal API for Badoo applications we found those approaches to be too limiting. Passing version number requires implementers to accommodate for all breaking changes when bumping version – even when it’s not required for business goals of that application at the time. Instead of driving value for business, application developers are in constant race to keep up with the API.
Never introducing incompatible changes is also not an option. After several feature redesigns (something that may happen at Badoo once every few weeks) protocol becomes bloated and half of the fields transmitted over the wire start being useless.
This talk is about our approach to versioning as part of client-server component negotiation. Client announces features and capabilities it supports and server replies with features status: whether they are enabled or disabled and whether they can be enabled by some user action (e. g. by buying some paid product).
Beside those componentized features, client also sends support flags such as SUPPORT_IMAGE_SIZE_VIA_URL which affects how API works. We use those flags where in typical API a version number bump would be required.
This approach allows both server and client to understand their current state and adjust their code accordingly – essentially, a tailor-made API for every client. Gathering data on feature and flag support among clients allows us to remove old code branches while continuing to evolve the API.
As a result, we are not afraid to change something when that change is required. Old clients continue to work while protocol rot is kept at low level.
In this talk I will give details on how exactly this versioning scheme work, how we test those changes, how and when we deprecate our old clients and note some stats and insights from using this scheme at Badoo for several years.
Automating the API Product Lifecycle
Looking at the full API Product Lifecycle, from defining an API and implementing the API, to launching with a solid developer site and experience, let’s see the newest tools - and potentially upcoming opportunities - to automate the creation of a solid developer experience.
Creating a successful API requires a proper process from concept and design, through development, and into ongoing maintenance and responsive developer support. As developer expectations for better-quality APIs increase, tools have made it easier to implement this well. Thanks to standards like OpenAPIs, it’s easier to create a quality API, developer site, and overall experience. Many of us create API documentation or code libraries automatically from an OpenAPI spec, but there’s a lot more coming along to make our lives easier, and to make our APIs look better. In reviewing the full API Product Lifecycle to design an API people will use, let’s see the newest tools - and potentially upcoming opportunities - to better automate the creation of a compelling developer program.
Continuous Delivery: Fly the Friendly CI in Pivotal Cloud Foundry with Concourse
This document provides an overview of continuous integration (CI) and continuous delivery (CD) using Concourse. It introduces Concourse and discusses why containers and pipelines are useful for CI/CD. It then demonstrates how to use Concourse in practice with examples and explains how to get started using Concourse for CI/CD workflows. The key aspects covered are Concourse's simple and scalable pipeline model using resources, tasks, and jobs, how containerization provides dependable and isolated executions, and how pipelines allow flexible yet efficient software testing and deployment.
Continuous Integration
Continuous integration involves integrating code changes frequently - usually multiple times per day - by having an automated build and test process. This helps reduce integration problems and leads to more cohesive software. Best practices include having a single source repository, automated builds and tests, fixing broken builds immediately, and keeping the build process fast. The document then provides examples of continuous integration pipelines at Alea using tools like Docker, Jenkins, and custom scripts to build and test Python and Golang components and libraries. It emphasizes automating everything and following best practices to implement continuous integration effectively.
What's hot (20)
Anatomy of a Continuous Integration and Delivery (CICD) Pipeline
Anatomy of a Continuous Integration and Delivery (CICD) Pipeline
Why You Need a Developer Relations Team for Your API
Why You Need a Developer Relations Team for Your API
Enterprise E-commerce Webinar Series, Episode 2: Deploying and Monitoring You...
Enterprise E-commerce Webinar Series, Episode 2: Deploying and Monitoring You...
Azure Integration DTAP Series, How to go from Development to Production – Par...
Azure Integration DTAP Series, How to go from Development to Production – Par...
QConSP 2014 - Continuous Delivery - Part 03 - Continuous Integration
QConSP 2014 - Continuous Delivery - Part 03 - Continuous Integration
Logic apps and PowerApps - Integrate across your APIs
Logic apps and PowerApps - Integrate across your APIs
Versioning strategy for a complex internal API (Konstantin Yakushev)
Versioning strategy for a complex internal API (Konstantin Yakushev)
Continuous Delivery: Fly the Friendly CI in Pivotal Cloud Foundry with Concourse
Continuous Delivery: Fly the Friendly CI in Pivotal Cloud Foundry with Concourse
Similar to Mobile Apps CI
03 02 - tizen app development with visual studio mobile center and team services
The reference process of Tizen app development on the base of Tizen-compatible life cycle and continuous integration services, provided by Microsoft Visual Studio in partnership with Samsung.
The Mobile Center Tizen SDK offers device side API for collecting app running time statistics and observing it on the Mobile Center Web UI.
The Team Services supply build task queue, which automatically builds, signs and deploys Tizen app right after the app sources are submitted to the online repository.
DevOps & DevEx
DevEx aims to improve the developer experience by focusing on tooling, technologies, and documentation within a DevOps environment. This includes adopting integrated toolchains that streamline the development lifecycle through automation and by ensuring tools are well-tested, configurable, and have comprehensive documentation. The goal of DevEx is to create an optimal software production environment by minimizing friction between development, testing, and operations teams through collaboration, shared tools, and improved processes.
Code in the Cloud - December 8th 2014
Code in the Cloud presentation as presented in Antwerp Lindner Hotel on 8th December 2014
#codeinthecloud
Agenda from the event:
In the AM (Introduction)
- Introduction to Application Lifecycle Management and Visual Studio Online
- Managing your project: what, who and when
- Working with code: keeping the source code safe and in-sync and be productive as a developer
- Tracking progress: how are we doing
- Improving quality: continuous build, deploy and testing
EAT
In the PM (Putting it all into practice)
- Exciting demonstrations and walkthroughs on how to run your project with Visual Studio Online.
Exercising and Scaling Up Mobile DevOps in the Enterprise
Adopting the mobile devops culture, processes and practices in any organization may not happen overnight. The transformation from agile to true mobile devops requires identification of inefficiencies and understanding of how process, practice and infrastructure can be scaled up.
Stay tuned and join our upcoming webinars at bitbar.com/testing/webinars/
Continuous Integration: A Case Study
Session Presented at 2nd IndicThreads.com Conference On Software Quality held on 25-26 March 2011 in Pune, India
WEB: http://Q11.IndicThreads.com
UiPath Task Capture training.pdf
With Task Capture, you can easily bridge the documentation gap between Process Experts and RPA developers to accelerate automation development and process improvements. We will explore the following:
1. Introduction to Task Capture
2. How to set up Task Capture
3. Demo 1- Task Capture by recording
4. Demo 2- Task Capture by Building from Scratch
5. Generating and Sharing process documents
👨💻👩💻 Explore UiPath Task capture further and follow-up on today's meetup:
✔ UiPath product suite: https://www.uipath.com/product/task-capture
✔ UiPath Academy: https://academy.uipath.com/learningpath/uipath-task-capture-2
✔ UiPath Forum: https://forum.uipath.com/tag/uipath-task-capture
PratheshBV_Resume
This document contains a resume and summary of qualifications for Prathesh B V. He has over 50 months of experience in information technology, including experience with software development, continuous integration tools, UNIX/Linux systems, and banking application implementations and automation. His experience includes roles at Cognizant Technology Solutions and Polaris Financial Technology. He holds a Bachelor's degree in Computer Science and Engineering.
Working Agile with Scrum and TFS 2013
This document provides an introduction and overview of agile project management methodologies like Scrum and how they can be used with Visual Studio Online 2013. It discusses the principles of agile, describes Scrum roles and processes, and explains how Visual Studio Online supports agile development with tools for planning, tracking work items, version control, continuous integration and more. The document aims to help Egyptian automation testers work agilely using Scrum and the cloud-based tools in Visual Studio Online.
Office Add-ins community call-March 2019
Agenda summary:
-Doug Mahugh: High-level overview of Office (web) Add-ins
-Sohail Zafar: What’s new with Outlook JavaScript APIs
-Nitesh Golchha: Office Add-ins Single Sign-On (SSO)
-David Chestnut: Office Add-ins Patterns & Practices
-Sudheer Maremanda: Edge WebView control for the Office Add-ins platform
-Mark Roden of PSC Group: Office Add-in demo (Word & SharePoint integration)
Practicing Agile in Offshore Environment by Himanshu Seth & Imran Mir
AgileNCR 2010 conference was held in Gurgaon on 17th & 18th July 2010. This largest community driven conference was the Fourth edition of Agile NCR and was organized in collaboration with ASCI. This time the event was based on four major themes : 'Agile for newbies', ' Agile Adoption Challenges', 'Workshops and Software Craftsmanship', and ' Post Agile'.
Cloud continuous integration- A distributed approach using distinct services
In cloud computing services the ability to share and deliver services, scale computing resources and distribute data storage and files requires a deployment process aligned with agility and scalability. The continuous integration can automate process reducing operational effort, improving code quality and reducing time to market. This presentation shows a proposal for distributed continuous integration to use differents cloud computing services, from planning to execution of scenarios.
Bitrise: How to make iOS builds faster - Tokyo 2019 March - Eureka meetup
Viktor Benei discusses several techniques for speeding up iOS builds on Bitrise, ranging from using more powerful machines to caching and parallelization. Some key recommendations include using Linux stacks when possible, caching common steps like dependency management, keeping caches small, triggering parallel workflows, and pre-booting simulators. Removing unnecessary steps can also improve build times.
Sam segal resume
This resume summarizes Sam Segal's experience as a software developer and systems engineer. He has over 15 years of experience building applications using technologies like Java, Spring, React, and Docker. His most recent role involved upgrading a startup project from Spring MVC to a Spring Boot REST API with a React frontend. He has extensive experience developing both web and mobile applications.
Presentation 1 open source tools in continuous integration environment v1.0
The document discusses open source tools that can be used in a continuous integration environment. It provides an overview of build tools like Ant and Maven, continuous integration servers, and how tools like Hudson and Archiva can help manage builds, artifacts, and the development process in an agile workflow.
Automation in iOS development
Be productive with automation.
Introduction to Fastlane, Match, Rome, and Bitrise for iOS development teams.
Azure CICD - Day1.pptx
This document provides information about a webinar on CI/CD pipelines for UiPath process deployment using Azure DevOps. The webinar will include introductions to Azure DevOps and setting up a UiPath environment with it, building CI/CD pipelines for UiPath automation, and a demo. It defines CI/CD and discusses how it applies to RPA tool UiPath. It also outlines the key components of Azure pipelines like triggers, jobs, stages, and artifacts. Finally, it mentions there will be hands-on configurations of agents and creating pipelines and releases in Azure DevOps.
Advanced Strategies for Testing Responsive Web
This document outlines an agenda for a webinar on advanced strategies for testing responsive web applications. The webinar will cover key recommendations for testing responsive web designs at scale using automation and visual testing techniques. It will also discuss opportunities for improving performance and optimization of responsive web sites. The webinar will include demonstrations of automating tests across desktop and mobile browsers in parallel using cloud infrastructure as well as visual testing techniques using AI.
Ship code like a keptn
Keptn is an open-source project that provides tools to enable continuous delivery and automation for modern applications using Kubernetes. It allows developers to focus on code and DevOps teams to focus on tools rather than building custom pipelines. Keptn provides automated multi-stage delivery pipelines, automated quality gates, self-healing deployments, and enables zero-touch toolchain integration and updates. It also supports automated problem remediation in production for continuous operations. Keptn follows cloud-native design principles and provides a common way for organizations to achieve autonomous delivery and operations.
Mobile App Quality Roadmap for DevTest Teams
Join Perfecto & CloudBees for a presentation on how to drive mobile app quality feedback in every build, on real devices. Watch a demo featuring the CloudBees Jenkins Workflow showcasing automated testing with Perfecto's Continuous Quality Lab.
From 0 to DevOps in 80 Days [Webinar Replay]
From 0 to DevOps in 80 Days
Link to the webinar replay: https://info.dynatrace.com/apm_dtm_ops_17q3_wc_from_enterprise_tocloud_native_na_registration.html
“Innovate or die” may sound extreme, but it’s the only way to thrive in today’s ever competitive market. Bernd Greifeneder, CTO of Dynatrace, wanted to ensure that the company was relevant 5 years from now so he formed an internal incubator with one goal: transform Dynatrace into a Cloud Native DevOps organization.
The incubator focused on what the company needed to do in order to integrate nascent cloud technologies so that they wouldn’t be left in the dust when the inevitable tipping point to cloud arrives. Transforming into a cloud native company would allow for rapid release cycles and provide an embedded feedback loop.
The Results: Dynatrace now has a 99.998% availability of SaaS Service and can deploy changes within an hour if necessary. In parallel, a new SaaS and managed offering is released every 2 weeks with 170 production updates per day.
Watch this recorded webinar as Bernd Greifeneder shares the lessons learned moving Dynatrace from an on-prem company to one that is cloud native.
Bernd discusses:
• The driving factors that led to the transformation
• The goals that were set back in 2011 towards the engineering team
• How to sell such a transformation project in a large enterprise organization
• How to support this multi-year project from top down without impacting regular operations
• What's next on the innovator's mind
Similar to Mobile Apps CI (20)
03 02 - tizen app development with visual studio mobile center and team services
03 02 - tizen app development with visual studio mobile center and team services
Exercising and Scaling Up Mobile DevOps in the Enterprise
Exercising and Scaling Up Mobile DevOps in the Enterprise
Practicing Agile in Offshore Environment by Himanshu Seth & Imran Mir
Practicing Agile in Offshore Environment by Himanshu Seth & Imran Mir
Cloud continuous integration- A distributed approach using distinct services
Cloud continuous integration- A distributed approach using distinct services
Bitrise: How to make iOS builds faster - Tokyo 2019 March - Eureka meetup
Bitrise: How to make iOS builds faster - Tokyo 2019 March - Eureka meetup
Presentation 1 open source tools in continuous integration environment v1.0
Presentation 1 open source tools in continuous integration environment v1.0
Mobile Apps CI
- 1. Mobile Apps CI | | Ahmed Shady STCian Mobility Team|05/03/2017
- 2. Agenda CI/CD: What/Why? Git: Which Workflow? Fastlane: Automation done right. Jenkins: Automation Server. Demo: yes, it is easy as this!
- 3. Continuous Integration / Delivery Why? ● Catching problems quickly, easily, and early ● Enhancing collaboration ● Broadening test coverage ● Generating build and test statistics over time ● Saving your effort/time.. What? The process of automating and streamlining the ● building ● analyzing ● testing ● archiving ● publishing of your App (life)
- 4. Git Workflows 1. Centralized Workflow Source: https://www.atlassian.com/git/tutorials 4. Forking Workflow 2. Feature Branch Workflow 3. Gitflow Workflow
- 5. Git Workflows 1. Centralized Workflow Source: https://www.atlassian.com/git/tutorials 4. Forking Workflow 2. Feature Branch Workflow 3. Gitflow Workflow 1. Centralized Workflow Your team can develop projects in the exact same way as they do with Subversion
- 6. Git Workflows 1. Centralized Workflow Source: https://www.atlassian.com/git/tutorials 4. Forking Workflow 2. Feature Branch Workflow 3. Gitflow Workflow 2. Feature Branch Workflow All feature development should take place in a dedicated branch instead of the master branch. This encapsulation makes it easy for multiple developers to work on a particular feature without disturbing the main codebase. The master branch will never contain broken code Encapsulating feature development also makes it possible to leverage pull requests
- 7. Git Workflows 1. Centralized Workflow Source: https://www.atlassian.com/git/tutorials 4. Forking Workflow 2. Feature Branch Workflow 3. Gitflow Workflow The Gitflow Workflow defines a strict branching model designed around the project release. While somewhat more complicated than the Feature Branch Workflow, this provides a robust framework for managing larger projects. Feature Branch Workflow + It assigns very specific roles to different branches and defines how and when they should interact It uses individual branches for preparing, maintaining, and recording releases.
- 8. Git Workflows 1. Centralized Workflow Source: https://www.atlassian.com/git/tutorials 4. Forking Workflow 2. Feature Branch Workflow 3. Gitflow Workflow Developers push to their own server-side repositories, and only the project maintainer can push to the official repository. This allows the maintainer to accept commits from any developer without giving them write access to the official codebase.
- 9. Fastlane ● Save days of preparing app submission, uploading screenshots and releasing the app ● Colleague on vacation and a critical bugfix needs to be released? Don’t rely on one person (Sul… ) releasing updates ● Increase software quality and reaction time with more frequent and smaller releases ● Ship your mobile app from any computer or server The easiest way to automate building and releasing your iOS and Android apps lane :appstore do increment_build_number cocoapods scan snapshot sigh deliver sh "./customScript.sh" slack end Automation done right
- 10. Fastlane family iOS Android Command line tool for updating Android apps and their metadata on the Google Play Store Automate taking localized screenshots of your Android app on every device Automatically create and maintain iOS code signing certificates Because you would rather spend your time building stuff than fighting provisioning The easiest way to run tests of your iOS and Mac app The best way to manage your TestFlight testers and builds from your terminal Building your iOS app has never been easier and more..
- 11. Jenkins Jenkins is an open source automation server with an unparalleled plugin ecosystem to support practically every tool as part of your delivery pipelines
- 12. Demo time... Life is too short to do this yourself