简体   繁体   English

用于发布管理的Gradle构建变体和风味

[英]Gradle Build Variants and Flavors for and Release Management

We have started building a new (the first from our team) android application. 我们已经开始构建一个新的(我们团队中的第一个)Android应用程序。 I want understand the release mechanism for the Android development. 我想了解Android开发的发布机制。 Say we have release some version 1.1.0.1 and now we have decided to go to a new major version 2.0.0.0 with lots of new features and completely reworked UI. 假设我们已经发布了1.1.0.1版本,现在我们决定使用具有许多新功能和完全重新设计的UI的新主版本2.0.0.0。

It is assumed that this whole process will be taking a lot of time, sufficient enough for the previous major to be able to attract a few enhancements or fixes. 假定整个过程将花费大量时间,足以使以前的专业能够吸引一些增强或修复。

Now in my previous experience with .net and all we used source control branch for the new build and keep pushing the required modification to the old branch and created a tag out of it every time a new release is created and once the another major version is released the branches are merged together and a new tag is released from there. 现在,根据我以前对.net的经验,我们将源代码控制分支用于新的版本,并继续将所需的修改推送到旧分支,并在每次创建新版本时以及在创建另一个主要版本时在其中创建一个标记。释放分支合并在一起,并从那里释放一个新标签。

This all merging pulling/pushing of code requires a great effort and a keen eye to keep up the Source Control neat and clean. 将所有这些合并的代码拉入/推入操作都需要付出巨大的努力,并且需要敏锐的眼睛来保持Source Control的整洁和干净。

With the start of Android and Gradle build variant and flavor option, is there anything possible to keep the common code in a single place for the enhancements so that anything which we require to be available in both the builds are kept there. 随着Android和Gradle构建变体和风味选项的开始,是否有可能将通用代码放在单个位置以进行增强,因此我们需要在两个构建中都可用的所有内容都保留在那里。 And only the features and code required in the new major build goes in there. 而且只有新的主要版本中所需的功能和代码才能进入其中。

Please let me know if I am making any sense here or you are seeking more clarity on the question. 如果我在这里有任何道理,或者您正在寻找一个更清晰的问题,请让我知道。

I will be glad to find out the ways to effectively manage the code here. 我将很高兴在这里找到有效管理代码的方法。

Anant, imho GitFlow Workflow is the best solution to adopt (and is not old school!!!) Anant,恕我直言,GitFlow工作流程是采用的最佳解决方案(而不是老派!!!)

Read the End-user discovers a bug chapter of this link ; 阅读最终用户发现 此链接 的错误章节;

With this workflow you can have your hot-fixes in master and develop branch just by closing the hot-fix. 使用此工作流程,您只需关闭修补程序即可将修补程序保存在master和develop分支中。 Try it! 试试吧!

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM