Connect Your Mobile App CI/CD to AppShare
Wire AppShare into the pipeline you already have, built for mobile app CI/CD, whether that's GitHub Actions or a Bitrise alternative you're already running, and skip the manual upload step entirely. A push, a merge, or a tag triggers the release on its own, and testers get the link without anyone touching the dashboard.
The Basics
CI and CD Aren't the Same Thing
Continuous Integration (CI)
Merging code changes frequently, with an automated build and test on every change. This is the foundation of mobile app CI/CD, catching a broken build before it goes anywhere.
Runs on every push or merge
Compiles the code automatically
Confirms tests still pass
Catches a broken build early
Continuous Delivery (CD)
Picks up once CI confirms a build is good, and handles getting that build to the people who need it, instead of someone uploading it by hand.
Triggers right after CI passes
Automates the upload step
Removes manual handoff
Feeds straight into AppShare
UNDER THE HOOD
Every Integration Runs on AppShare CLI
Every snippet on this page is really AppShare CLI, called from your pipeline instead of your terminal. That’s true for GitHub Actions just as much as any other platform.
npm install -g zunoy-appshare-cli
Workflow
From Pipeline to Install Link
Four steps, added once, that turn your existing pipeline into a release process.
- 1
Build
Your existing build step runs on every push, producing the
.apkor.ipa. - 2
Integrate AppShare CLI
Add a step after it, install the CLI, then upload the file it produced. - 3
Configure the API Key
Store it in your CI provider's secrets manager, referenced, never hardcoded.
- 4
Trigger the Pipeline
Every future push runs build, then upload, automatically.

Integrations
Connect the Pipeline You Already Use
Seven platforms, from GitHub Actions app distribution to Fastlane, each with a ready-made step built for it.
GitHub Actions
Trigger a release directly from a workflow file, on push, pull request, or tag.
GitLab CI/CD
Add a job to your .gitlab-ci.yml that pushes a build the moment your pipeline reaches it.
Bitrise
Drop AppShare into a Bitrise workflow as a step, right alongside your existing build and test stages.
Xcode Cloud
Trigger an AppShare release from an Xcode Cloud workflow, without leaving Apple's own CI environment.
Fastlane
Add an AppShare lane to your existing Fastfile, alongside your build and signing steps.
Anything Else? Use the CLI Instead
If your pipeline isn’t one of the platforms above, AppShare CLI runs from any shell-based CI environment, and the Public API covers custom setups, such as a CI/CD IPA upload from an in-house build server.
Use Cases
Who Automates Releases With AppShare
- TEAMS
Engineering Managers
Standardize how the team ships, instead of one person remembering to upload after every merge.
- STARTUP
Startups Shipping Daily
Keep pace with a build that changes multiple times a day, without a manual step slowing it down.
- AGENCIES
Agencies Managing Clients
Run the same release step across every client project, instead of repeating it by hand for each one.
- REGULATED
Regulated Industries
Fintech and healthcare teams get a consistent, repeatable release process every single time, not a manual step someone could skip.
Quick Answers
What is mobile app CI/CD?
CI/CD for mobile apps is the practice of automatically building, testing, and delivering iOS and Android builds on every code change. CI compiles the app and runs tests on each push or merge. CD takes a passing build and gets it to testers. AppShare handles the CD side, uploading each .apk or .ipa and returning an install link.
How do I set up a CI/CD IPA upload?
Add a step after your iOS build that installs the AppShare CLI and uploads the .ipa it produced, with your API key stored in your CI provider’s secrets manager. Every push, merge, or tag then uploads the new build automatically. Ad hoc builds still need tester UDIDs in the provisioning profile before signing, so register devices first.
How does GitHub Actions app distribution work with AppShare?
Add an AppShare step to your workflow file after the build job, store the API key as a repository secret, and choose whether it runs on push, pull request, or tag. Each run uploads the .apk or .ipa and returns an install link for testers. The GitHub Actions setup page has a ready-made snippet to copy.
Which CI/CD platforms does AppShare support
AppShare has ready-made steps for GitHub Actions, GitLab CI/CD, Bitrise, Jenkins, CircleCI, Xcode Cloud, and Fastlane, all included on every plan. If your tool isn’t listed, the AppShare CLI runs from any shell-based CI environment, and the Public API covers custom setups. Either way, you copy one snippet into your pipeline instead of writing a script.
Is AppShare a mobile CI/CD pipeline tool?
AppShare is the delivery step in your mobile CI/CD pipeline, not the build server. Your existing tool, such as GitHub Actions or Bitrise, still compiles and tests the app. AppShare then uploads the finished .apk or .ipa, applies your release settings, and notifies testers, so you keep your current pipeline and add only one step.
GET STARTED
Let Your Pipeline Ship the Build
Pick your mobile CI/CD pipeline tool, copy the snippet, and every future release ships itself from there.
Free plan available
No manual upload after setup
Seven platforms supported