Automating your mac farm for iOS build and automation
•Download as PPTX, PDF•
0 likes•196 views
This presentation talks about how we automated our build infrastructure for iOS develepment
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Automating your mac farm for iOS build and automation
Similar to Automating your mac farm for iOS build and automation (20)
Recently uploaded
Recently uploaded (20)
Automating your mac farm for iOS build and automation
- 1. Automating your Mac farm for iOS build & automation Mikhail Advani & Sagar Maurya ThoughtWorks
- 4. Easiest Solution: Hosted CI
- 6. Limitations of Conventional Hosted CI ● Most of the hosted CI solutions have 4GB RAM macOS VMs ● Hosted CI is well suited for a monorepo.
- 7. Next most simple solution
- 8. But how can this be automated Vanilla OS Configuration Management Tool Execution+ Provisioned Build Agent
- 9. Typical tools that need to be installed/configured ● XCode ● Simulator Devices ● Git ● Build agent app ● Static Code Analyser ● Java/Ruby/Python with all the versions ● … ● … ● … ● ...
- 10. Vanilla OS + Provisioned Build Agent Configuration Management Tool Execution TIME!!!
- 11. Snapshot Restoration Machine Snapshot Restoration+ Provisioned Build Agent DeployStudio Server + Post Restoration Configuration
- 12. Snapshot Creation Vanilla OS Configuration Management Tool Execution+ Almost Provisioned Build Agent DeployStudio Server Snapshot Creation
- 13. Demo
- 14. Demo
- 15. What is Happening Now? Any Machine Deploy Studio Server
- 16. Additional Features offered by DeployStudio ● Network Configuration ● Script Execution ● Package Installation ● Network Backed Re-imaging ● And much more ...
- 17. Do we need to keep this inside the office? Rack in a self hosted data center could have been a solution but in certain scenarios physical co-location is needed with macOS: ● First login in the case of encrypted File Systems ● Granting privileges to access keychain ● Power reset after a machine just fails to respond
- 18. Problems with this local hardware ● Scale ● Cost ● High Availability ● Geographic availability ● Power ● Network Bandwidth ● Monitoring ● Cooling
- 19. Alternative Solutions ● Hosted mac service providers ● On-premise mac Cloud ● Cloud Device Farm(no builds, test automation only)
- 20. Hosted mac service providers ● Managed ● Cost ● Security ● Plan limited on-demand scaling
- 21. On-premise mac Cloud Hypervisor = Mac Pro
- 22. Public Cloud Setup ( automation only ) Container Hosting Service Device Farm
Editor's Notes
- What is build and automation Fast feedback
- Animate Build & Test -> Xcode -> MacOs -> Not provided by cloud providers iOS needs XCode to build Stable emulators for iOS test automation come with XCode XCode can run only on macOS(OSX) macOS can legally be run only on Apple Hardware Apple Hardware/macOS is not offered by the large Cloud Service Providers
- Why it is easiest solution ? Don’t need to worry about hardware configuration. Whatever tools you need. Just specify in your build scripts. Availability
- Why do we need multiple machines ? This solution offers a problem The problem is how do you make sure that there is no configuration drift. You have to install a package into 15 machine but left one by mistake.
- A hell lot of softwares.
- In the context of our setup.
- Disclaimer : We have masked out client sensitive information. You log into a machine Go to System Settings > Startup Disk You will see Deploy Studio Server in the list. Select it and choose to restart.