Exactly like MSBuild, Gradle allows to setup, trough properties and configuration files, complex build systems, which require additional tasks other than just compiling the source code. You can think of it like MSBuild, but for platforms different than C# and. It's a very popular build automation system, widely used for Java projects. If you have ever tried to deploy your React Native application on Android, you should already have met Gradle. Let's start to see how we can add Android support to our pipeline! The goal is to have a Windows, Android and iOS application automatically deployed every time I commit some code to the repository which hosts my React Native project. And thanks to native modules, we can also build plugins which, under the hood, use Android, iOS or Windows APIs to perform a task.Īs such, after having successfully built a CI/CD pipeline on Azure DevOps for automatically build and deploy my React Native project for Windows, I decided to move to the next step and build such a pipeline also for the other platforms. This is made possible by the different render targets, which translates the various JSX controls into native controls of the platform where the application is running. However, one of the advantages of React Native is the ability to target multiple platforms leveraging the same codebase and, at the same time, achieve the same quality of a native application. In the previous posts I have written on this blog I have talked about many specific tasks related to React Native for Windows: how to build a native module, how to setup a CI/CD pipeline on Azure DevOps, etc.
0 kommentar(er)
