E3DS Automation Tools listing on the FAB Marketplace shown on a desktop monitor

Make Deployment a Step in Your Pipeline

The Eagle 3D Streaming Automation Kit uploads a packaged Unreal build, registers it and waits for the stream test, all from a script. Shipping stops depending on someone sitting at a browser.

Trusted by Unreal developers to automate their app deployments to Eagle 3D Streaming

Metrotopia
Epic Games
Manual Deployment Bottlenecks

Why Deployment Still Waits on Someone

Every release to Eagle 3D Streaming needs a person to do it by hand: package the project, open the Control Panel in a browser, upload the build, then
check whether the stream test passed.
That works as long as someone is there to do it. A pipeline runs when nobody is. Nothing starts from a commit or a merge, the stream test result goes unrecorded, and the whole routine repeats on every branch, so the work grows as the team does.

  1. Package the project

    Build and package the latest Unreal Engine project changes.

  2. Open the
    Control Panel

    Sign in to the E3DS Control Panel to manage the application deployment.

  3. Upload
    the build

    Manually upload the packaged application as a ZIP archive.

  4. Watch it

    Launch the stream and manually check whether the application works as expected.

  5. Someone has
    to be there

    A developer must initiate and verify each deployment, repeating the process for every release.

CI/CD Automation

One Call From Your Pipeline

Your pipeline calls one function. It uploads the build, registers it, waits for the stream test, and prints the result where your build log picks it up.

YOUR PIPELINE STEP

Install from npm
const { uploadStreamingApp } = require("e3ds-automation-kit");

(async () => {
  await uploadStreamingApp(
    "./build/myApp.zip",       // your packaged build
    process.env.E3DS_API_KEY,  // from your secret store
    "MyStreamingApp"           // the name in your Control Panel
  );
})();

A single function handles the upload, application registration, and stream-test monitoring. Provide the packaged ZIP, API key, and application name to integrate deployment into your CI/CD pipeline.

WHAT LANDS IN YOUR BUILD LOG

[Uploader] Preparing upload for MyStreamingApp (600 MB / 0.59 GB)
[Uploader] Storage provider: r2
[#######...........] 50% | myAppBuild.zip | 300.00/600.00 MB
[Uploader] File upload complete.
[Uploader] Polling stream test result for MyStreamingApp_uv-1...
[Uploader] Stream test successful
Upload completed successfully!

Track upload progress, application registration, and stream-test status directly in your pipeline logs. Built-in retries help recover from temporary failures, while status messages provide visibility into the deployment process.

That is the whole integration.

Getting Started

Running It

Three steps from an empty project to a build in your Control Panel

  1. Install the
    package

    01

    Run npm install e3ds-automation-kit in the project your pipeline builds from.

  2. Point it at your
    build

    02

    One call with three things: the path to your packaged .zip, your API key and the app name.

  3. Run it

    03

    Call it with node as a pipeline step, the same as any other command in your build.

Keep your API key in an environment variable rather than the script, since in CI it belongs in the pipeline's secret store. Argument rules and troubleshooting are in the documentation.

Automation Capabilities

What It Handles For You

A Node.js package that runs the entire upload sequence in a single call

The Whole Sequence

Upload, register and stream test in one call. Nothing for you to wire together.

Storage Handled

Detects whether your account is on Cloudflare R2 or legacy storage and uses the right flow. Nothing to configure.

Survives a Bad Connection

Retries on its own when the network drops out, so a brief connection problem does not fail the build.

Results in Your Build Log

Progress while it uploads, then the stream test outcome printed to the console.

Automation Options

Which Tool You Want

Eagle 3D Streaming has two ways to automate an upload. The difference
is whether a person is there when the build ships.

  • This Plugin

    Automation Kit

    A pipeline ships your builds and nobody is watching. A Node package that runs the upload from a script, triggered by a commit, a tag or a schedule.

  • The Other Plugin

    Automation Tools

    You package by hand, from the editor. One click runs packaging, compression and upload without leaving Unreal. See the Automation Tools plugin ›

Windows packaged builds only

The Kit registers every upload as a Windows Unreal build. A Linux build cannot be uploaded with it.

Compatibility

What It Runs On

  • Installed from npm, runs anywhere Node runs

    Node.js

  • Windows: Packaged Unreal builds only

  • Any CI: It is a Node script, so it runs as a step in any pipeline

  • Storage provider detected automatically per account

    0 config