登录查看更多内容

How frequently should you run your mobile app's CI pipeline?

由人工智能和领英社区提供技术支持

If you are developing a mobile app for multiple platforms, you might be wondering how often you should run your continuous integration (CI) pipeline. CI is the practice of automating the building, testing, and deployment of your code, so that you can deliver quality software faster and more reliably. In this article, we will explore some factors that influence the frequency of your mobile app's CI pipeline, and how to balance them for optimal results.

此文章中的业界达人

由社区从 6 条内容中精选。了解更多

HARSHAVARDHANA K P

Technical Delivery || Certified Scrum Master? || Web & Mobile Apps || Application Security

1 Project size and complexity

One of the main factors that affects how frequently you should run your CI pipeline is the size and complexity of your project. Larger and more complex projects tend to have more dependencies, features, and potential bugs, which require more frequent integration and testing. However, running your CI pipeline too often can also have drawbacks, such as increased costs, resource consumption, and wait times. Therefore, you should find a balance between the frequency and the duration of your CI runs, depending on your project's needs and goals.

添加您的观点

HARSHAVARDHANA K P

Technical Delivery || Certified Scrum Master? || Web & Mobile Apps || Application Security
举报内容
In case of hybrid mobile app & teams are following Agile-Scrum, they should run the pipeline every sprint once as part of the Sprint deliverables which will helps the team to get the testing results & throughput of the Sprint as well. Generally Mobile apps are delivered in two platforms i.e., iOS & Android. With Single run of CI pipeline we can get all the test results for both the platforms.

已翻译

赞
Jackie Qi

Early stage company builder
举报内容
I genuinely believe that setting up a CI pipeline is a must-do for any project, no matter its size. Think about it - it's like having a safety net. It gives us that extra bit of confidence every time we deploy code, because it catches issues early on. And if you're worried about the cost, there are some really budget-friendly options out there. For instance, if you're into handling things in-house, you could just set up a Mac Mini with Fastlane. It’s pretty straightforward and efficient. On the other hand, if you're more inclined towards cloud solutions, Bitrise is a great pick. It's not just wallet-friendly; it's reliable and speedy too. So really, there's a way to make CI work for us without breaking the bank or compromising on quality.

已翻译

赞

2 Development team and workflow

Another factor that influences how often you should run your CI pipeline is the size and structure of your development team, and the workflow that you follow. If you have a large and distributed team, working on different features and branches, you might want to run your CI pipeline more often, to ensure that your code is always in sync and compatible. On the other hand, if you have a small and co-located team, working on a single branch, you might be able to run your CI pipeline less often, as long as you communicate and coordinate well. Additionally, you should consider the workflow that you use, such as agile, scrum, or kanban, and how it affects the frequency and scope of your CI runs.

添加您的观点

HARSHAVARDHANA K P

Technical Delivery || Certified Scrum Master? || Web & Mobile Apps || Application Security
举报内容
Yes. In case of larger team the development team will be working on multiple features in parallel. Not all the features will be readily available for the current CI pipeline. Hence clear demarkation should be there with the team whats goes in, in this release that should checked in to a branch for the CI pipeline. Other features which might not completed yet & may be planned for upcoming releases can wait till the current release completes.

已翻译

赞
?? John Legasse

Android Software Engineer @BNP - ????
举报内容
In a perfect world, you would like your CI to run as often as possible, everything you can delegate to it, is time you are not losing on your own development machine. In reality, it has a cost (maintenance, hardware etc). As a rule of thumb a good start would be to: - automate process: releases, running tests, regressions detection. - ensure quality, bug free code before it reach others as during a pull request. It's easier to fix a bug when it's isolated and scoped to a limited small changes than propagating it to the whole codebase and potentially blocking other developers.

已翻译

赞

3 User feedback and market demand

A third factor that affects how frequently you should run your CI pipeline is the feedback and demand that you receive from your users and the market. If you are developing a mobile app that is highly competitive, innovative, or user-centric, you might want to run your CI pipeline more often, to deliver new features, fixes, and updates faster and more frequently. This can help you gain an edge over your competitors, satisfy your users, and increase your retention and revenue. However, if you are developing a mobile app that is more stable, mature, or niche, you might be able to run your CI pipeline less often, as long as you maintain your quality and security standards.

添加您的观点

HARSHAVARDHANA K P

Technical Delivery || Certified Scrum Master? || Web & Mobile Apps || Application Security
举报内容
User feedback & market demands are very critical in case of Mobile Apps.Development team should have segregation of features & bugs(Critical, Not So Critical,) identified with priorities. Always its recommended to not to mix the Bugs & features in single release. New features can wait in case any critical issues exists in the app.Because, Mobile apps undergo a process of review from Apple App Store & Google Play Store before it is available to public.

已翻译

赞

4 Testing strategy and tools

A fourth factor that influences how often you should run your CI pipeline is the testing strategy and tools that you use for your mobile app. Testing is a crucial part of CI, as it ensures that your code works as expected, and that it does not introduce any errors or regressions. However, testing can also be time-consuming, expensive, and challenging, especially for mobile apps that need to run on different devices, operating systems, and configurations. Therefore, you should choose a testing strategy and tools that suit your mobile app's requirements, such as unit testing, integration testing, UI testing, or end-to-end testing, and that can run efficiently and effectively on your CI platform.

添加您的观点

HARSHAVARDHANA K P

Technical Delivery || Certified Scrum Master? || Web & Mobile Apps || Application Security
(已编辑)
举报内容
Testing the mobile apps are very critical by considering different platforms(Operating Systems such as iOS, Android) & device screen sizes. Always use both kinds of testing i.e., Manual & Automated test suite to get desired results. Some business scenarios might not be covered in Automated test cases, that should be covered in Manual testing. Tools such has Appium, Espresso etc. can be used for Automated tests.

已翻译

赞

5 CI platform and configuration

A final factor that affects how frequently you should run your CI pipeline is the CI platform and configuration that you use for your mobile app. There are many CI platforms and services available for mobile app development, such as Jenkins, GitHub Actions, Bitrise, or Firebase. Each of them has its own advantages and disadvantages, such as scalability, performance, reliability, security, and cost. You should choose a CI platform that meets your mobile app's needs and budget, and that can support the frequency and duration of your CI runs. Moreover, you should configure your CI pipeline to optimize your resources, such as parallelizing your tasks, caching your dependencies, and skipping unnecessary steps.

添加您的观点

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Mobile Applications

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How frequently should you run your mobile app's CI pipeline?

1

2

3

4

5

6

1 Project size and complexity

2 Development team and workflow

3 User feedback and market demand

4 Testing strategy and tools

5 CI platform and configuration

6 Here’s what else to consider

Mobile Applications

给文章评分

感谢您的反馈

更多Mobile Applications相关文章

更多相关阅读内容

How frequently should you run your mobile app's CI pipeline?

1

2

3

4

5

6

1 Project size and complexity

2 Development team and workflow

3 User feedback and market demand

4 Testing strategy and tools

5 CI platform and configuration

6 Here’s what else to consider

Mobile Applications

给文章评分

感谢您的反馈

查看其他技能