iOS — How to handle Semantic Auto-Versioning on CI
Unless you’re a Multimillion or a Billion dollar company, you probably don’t have a multimillion-dollar ad budget or professional Spinners. Your product needs to stand out on its own merits like App Quality, Performance, UI design, and User Experience. Most companies don't care about you, your product, and your vision or dreams. They don't give a damn about either their work helped you to get more business, revenue, users, or solving a problem. That's where CANOPAS comes into the picture. Whether you have a GREAT IDEA and you want to turn it into a DIGITAL PRODUCT. OR You need a team that can turn your NIGHTMARES into SWEET DREAMS again by improving your existing product. We help Entrepreneurs, startups, and small companies to bring their IDEA to LIFE by developing digital products for their business. We prefer using Agile and Scrum principles in project management for flexibility and rapid review cycles. We are not bound by technology. We will learn new technology if it significantly improves the performance of your app. We will solve your tech-related problems even though we are not THE EXPERT in it. And we've done it multiple times in the last 7 years. In the last seven years, we helped... A STARTUP to expand its users from 2500 to over 100000 by developing mobile apps for them. An enterprise client to redevelop their app that has 1M+ monthly paid users and 10M+ app downloads. Another enterprise client(5M+ app downloads in each store) to fix bugs and broken parts in the app and as a result, they had over 98% crash-free users. We offer a 100% MONEY BACK GUARANTEE if you don't like our work. No questions asked. Visit : https://canopas.com/blog
Want to automate your deployment with auto-versioning and save 25% of your time?
In this article we’ll explore How to handle Semantic Auto-Versioning on CI. We will follow semantic versioning.
Basically, the version name will be created with the combination of major, minor, and patch numbers.
For example, for app version 1.4.0 —
1 - major number 4 - minor number 0 - patch number
If we want to auto-deploy apps on every commit, we can keep major and minor versions static. Make the patch number dynamic.
For patch number, we can use the pipeline ID which changes with every commit, thus every build with have a unique version name and number.
We will need to make 3 changes in our project to support auto-versioning.
- Add VERSION file
- Update deployment script
- Update Project files
Once done, you will never have to worry about pushing build on CI. Commit your changes and you will have a build ready on Testflight within a few minutes.
For implementation details, visit our blog.
