GitLab CI/CD

From CircleCI Job to Install Link

Q: Where does the AppShare job go?

In .circleci/config.yml, as a new entry under jobs:, referenced from a workflows: block.

Q: What triggers the release job?

Whatever you define under filters in the workflow, most commonly a specific branch, though tags and other conditions work too.

Q: Can I gate the release behind other jobs passing first?

Yes, using requires: in the workflow, so push_to_appshare only runs after your build and test jobs succeed.

Q: Can I add release notes automatically?

Yes, using the --notes flag on the upload command, either a static string or a value built from a CircleCI-provided variable like the commit SHA.

Drop AppShare into your `config.yml`, and a build ships the moment your workflow reaches that job, no separate tool, no manual step waiting at the end of the pipeline.

Start Free

What You Get

Three Reasons Teams Automate This Job

Keeps Pace With a Fast Pipeline

CircleCI is built around quick feedback and caching, adding AppShare as a job doesn't slow that down, it just adds one more thing that happens automatically.

Fits Into an Existing Workflow

If you're already orchestrating multiple jobs with workflows, the release job slots in as one more step with its own filters and dependencies.

Starts From a Clean Environment Every Time

Each job runs in a fresh Docker image, so there's nothing left over from a previous run that could affect the upload.

SETUP

Add AppShare to Your CircleCI Config

Push a build from a CircleCI job automatically as part of your existing pipeline.

Open .circleci/config.yml

Step 1

Find your config file under the .circleci folder.

Set your API key in Environment Variables

Secret

In Project Settings → Environment Variables, add APPSHARE_TOKEN.

Add the upload job

Pipeline

Add the upload job to your CircleCI workflow.

Commit & Push

Deploy

Push your changes to trigger your CircleCI pipeline.

Step 1 of 4

Step 1

Open .circleci/config.yml

Open .circleci/config.yml at your repository root.

.circleci/config.yml

version: 2.1
jobs:
  # Your existing build and test jobs

LIFECYCLE

What Actually Happens on a Run

Pipeline Kicks Off

A push to main starts the pipeline, and the releaseworkflow evaluates which jobs should run.

Executor Builds the App

CircleCI starts a fresh container or macOS executor and runs the real build command, producing the actual file.

AppShare CLI Installs

The install step runs fresh inside that executor, every single time.

Build Gets Pushed

The CLI reads the environment variable and uploads the file the build step just produced.

UNDER THE HOOD

CircleCI Just Runs the CLI

The job you added is just AppShare CLI, executing inside CircleCI instead of your terminal.

SEE CLI

Not Using CircleCI

AppShare Works With Your Pipeline Too

GitHub Actions

Trigger a release directly from a workflow file, on push, pull request, or tag.

Learn More

Bitrise

Drop AppShare into a Bitrise workflow as a step, right alongside your existing build and test stages.

Learn More

Jenkins

Add an AppShare step to a Jenkins pipeline, scripted or declarative.

Learn More

GitLab CI/CD

Add a job to your .gitlab-ci.yml that pushes a build the moment your pipeline reaches it.

Learn More

Xcode Cloud

Trigger an AppShare release from an Xcode Cloud workflow, without leaving Apple's own CI environment.

Learn More

Fastlane

Add an AppShare lane to your existing Fastfile, alongside your build and signing steps.

Learn More

FAQ

Questions About the CircleCI Integration

Where does the AppShare job go?

In .circleci/config.yml, as a new entry under jobs:, referenced from a workflows: block.

What triggers the release job?

Whatever you define under filters in the workflow, most commonly a specific branch, though tags and other conditions work too.

Can I gate the release behind other jobs passing first?

Yes, using requires: in the workflow, so push_to_appshare only runs after your build and test jobs succeed.

Does this work for both Android and iOS builds?

The job doesn't care either way, it just uploads whatever file path you give it, an .apk from a Docker executor or an .ipa from a macOS one.

Is CircleCI integration included on the Free plan?

It's bundled with CI/CD access generally, so it's there from the Free plan onward, not held back for a higher tier.

How do I keep my API key out of the config file?

Add it in Project Settings → Environment Variables, or in a Context if you want to share it across multiple projects, then reference it as $APPSHARE_API_KEY in your run step.

Which executor should the release job use?

A Docker executor is enough, since the job only needs to install the CLI and upload a file, no need for a full machine or macOS executor unless the rest of your build already requires one.