The Android build process is fairly complex: quite a few tools are invoked one after another: javac to compile, then dx to convert to dex, then aapt to package (I'm sure missing a few). You can run Ant in debug mode to see the exact sequence (it is also documented, somewhere...). So you can either:
Bundle the Ant jars with your app and invoke Ant programatically
Write a Java 'script' that invokes the tools in the correct order
Write a simple shell script/batch file and be done with it.
I am currently using Fastlane to automate beta and production releases. Fastlane is largely written in Ruby and you can customize releases based on your internal processes. You can watch this Droidcon '16 video to get started.
发布评论
评论（4）
我使用 ant 来完成此操作，我们使用 Jenkins 进行持续集成。我写了一篇关于如何自动化此操作的文章。
http://www.multunus.com/ 2011/09/持续交付-for-android-apps-part-1/
I've used ant to do this and we use Jenkins for Continuous Integration. I've written a post on how to automate this.
http://www.multunus.com/2011/09/continuous-delivery-for-android-apps-part-1/
我使用 Maven 和 Android 插件。效果很好。
请参阅 http://simpligility.github.io/android-maven-plugin/ 。
I use Maven with the Android plugin. It works well.
See http://simpligility.github.io/android-maven-plugin/.
Android 的构建过程相当复杂：一个接一个地调用相当多的工具：javac 进行编译，然后 dx 转换为 dex，然后 aapt 进行打包（我肯定缺少一些）。您可以在调试模式下运行 Ant 以查看确切的序列（它也被记录在某处......）。
因此，您可以：
The Android build process is fairly complex: quite a few tools are invoked one after another: javac to compile, then dx to convert to dex, then aapt to package (I'm sure missing a few). You can run Ant in debug mode to see the exact sequence (it is also documented, somewhere...).
So you can either:
我目前正在使用 Fastlane 来自动化
beta和生产版本。 Fastlane 大部分是用 Ruby 编写的，您可以根据内部流程自定义版本。你可以观看这个Droidcon '16 视频以开始使用。I am currently using Fastlane to automate
betaandproductionreleases. Fastlane is largely written in Ruby and you can customize releases based on your internal processes. You can watch this Droidcon '16 video to get started.