GitHub actions can now run these commands on our code in the cloud, on certain triggers such as when someone pushes to a branch, or when a PR is raised, or when a PR is merged, etc.įor this, we have defined separate. We have defined a set of actions (lint checks, code analysis, unit tests, JaCoCo code coverage, publishing to maven central) inside our SDK code that can be run via Android Studio’s Gradle or Gradle installed on any computer via command line. How are GitHub Actions Used by CleverTap’s Android SDK? There are many use cases and events which we can combine to get the outputs we desire. We can create workflows that build and test every pull request to our repository or deploy merged pull requests to production. ![]() GitHub Actions is a continuous integration and continuous delivery (CI/CD) platform provided by GitHub that allows us to automate our build, test, and deployment pipeline. ![]() ![]() Together, these two make the backbone of the modern DevOps Environment. IntroductionĬI/CD stands for continuous integration (CI) and continuous delivery (or deployment) and is a term given to a set of strategies and processes for a fast, reliable, and an effective development process of a software product. ![]() The following article aims to go through various concepts and challenges involved in the process. We recently incorporated a CI/CD pipeline in our core Android SDK, and it has given us significant results. Creating a CI/CD Pipeline For Android SDK Using GitHub Actions
0 Comments
Leave a Reply. |