Sitemap
Guy Lis

Guy Lis

Senior Mobile Developer at Unity | Developing a Mobile SDK for native Android & IOS

Jenkins vs GitHub Actions

4 min readApr 6, 2025

--

Press enter or click to view image in full size

Background

In a world where we develop for mobile apps, mobile sdks, servers or any other types of software components, coding is not enough. Our code needs to be verified, built, and deployed in a scalable manner. For this, there are Continuous integration/Continuous deployment automation servers dedicated for this purpose that most companies use. In the past, dedicated teams handled this aspect of development. Today, more and more of this responsibility falls under the developers working on the code.

Motivation

In order to give some examples of what these CI/CD servers can perform, I’ll share from my experience working on an SDK for mobile apps:

  • Build the SDK using a repository that contains its code and an application running it, either from a user prompt, in a scheduled mechanism or from various triggers like a pull requests.
  • Run various verifications such as unit tests, integration tests and automation tests on the code prior to updating it in the remote repository/when opening a pull request.
  • Format/Validate the code using some sort of code formatter to align it between all the developers.
  • Prepare a release candidate for the sdk based on a branch in the repository holding the relevant code along with an incremented version.
  • Publish the release candidate via maven central for android, ios for cocoa pods, swift package manager.

Different CI/CD server implementations

I have worked on several CI/CD servers including Jenkins, GitHub Actions and Yamato. There are also many others such as circleCI, Bitrise, Azure devops, Gitlab and more. In most cases where you work in a company, you don’t get to choose the server. In others, the decisions leading from one to another can change over time. The decision can be affected by questions such as :

  • Whether the server is self managed or self hosted.
  • How many people are going to use this server.
  • Special requirements from this server operating systems like a Mac, Unity.
  • Which other platforms is the team working with that will work in collaboration, for example what is used for code reviews or for storing the code base.

Jenkins Pros/Cons

Pros

  • Open-Source — flexibility to have something matching your needs
  • Stability in relation to downtime — The server is self managed so if there is any downtime or issue, you have more flexibility on handling it.
  • UI Flexibility — Jenkins provides more flexibility in UI customization for workflows compared to GitHub Actions.
  • Scalability — enabling distributed builds across multiple machines for improved speed and can also use cloud environments such as AWS.

Get Guy Lis’s stories in your inbox

Join Medium for free to get updates from this writer.

Cons

  • Maintenance — since the server is self managed, you are responsible for upgrading the machines the server is installed on and the server version itself meaning additional cost.
  • Complex setup — a lot of manual installation and configuration is needed.
  • Outdated UI/UX — compared to modern CI/CD tools
  • Troubleshooting self-hosted runners is challenging, and diagnosing infrastructure failures, such as plugin issues, can be time-consuming.
  • No native integration with supporting systems — unlike github actions, there’s no built in integration for a system needed for code storage or code reviews.
  • Security management — since Jenkins is self-hosted, you are responsible for securing it.

GitHub Actions Pros/Cons

Pros

  • Github integration — When working with git as your code repository as well as for code reviews, GitHub Actions integrates well for both. No need for additional external integrations.
  • Maintenance — Since GitHub Actions is a cloud-based solution, you do not need to manage server infrastructure
  • Pre-build actions — ability to automate common tasks instead of writing your own.
  • Flexibility in defining workflows — using YAML files allowing modular design and reusable actions.
  • Monitoring — have detailed logs for troubleshooting and the UI show the workflow progress, making it easy to track build failures.
  • Workflow optimization — support both parallel runs, scheduled runs and dependencies between workflows.

Cons

  • Handling downtime — there is little you can do when issues arise.
  • The UI is limited — GitHub Actions does not have too much Options UI related, e.g. you cannot create a workflow with more than 10 input fields.
  • Limitation for debugging — Debugging workflows is limited since testing must be done remotely rather than locally.
  • Workflow management — the yml syntax used for the workflows is limited compared to programming languages and be hard to maintain for large projects.
  • Performance — GitHub-hosted runners have performance limitations compared to self-hosted runners.

Migrating from one to another

I was part of migrating from Jenkins to GitHub Actions. Some tips I can share on this:

  • Break the migration into smaller steps, considering platforms and CI processes separately.
  • For multiple platforms, maintain a consistent CI/CD implementation across them, except where platform-specific adjustments are necessary.
  • This type of migration is hard to validate, so make sure to have a backup of all migrated processes in the old infra available as well as an easy way to revert a change if needed.

Conclusion

While working with a CI/CD server may not be as exciting as coding and leans more toward DevOps than traditional software engineering, it is an increasingly valuable skill for developers. Just as programming languages evolve — such as the shift from Java to Kotlin in Android or Objective-C to Swift in iOS — CI/CD tools also change over time. Being adaptable and ready to transition between different CI/CD solutions is essential in a fast-moving development environment

--

--

Guy Lis
Guy Lis

Senior Mobile Developer at Unity | Developing a Mobile SDK for native Android & IOS