Automated Flutter-Ionic Build Pipeline

Job ID: 39830890

Budget: $250 – $750 USD

I need a reproducible build pipeline that turns one command into fully versioned mobile artifacts and exposes the whole flow through a small, documented API.

Project Document: https://docs.google.com/document/d/1gx19axuAPWjPv3NlpAEPGSgRNBtQa45CZpG487kbEaU/edit?usp=sharing

Here’s what has to happen end-to-end.

• Kick off a Flutter build entirely by script. The build must stamp a semantic version and produce Android (APK/AAB) and iOS (IPA) outputs in a predictable folder structure.
• Drop the compiled Flutter bundle into a lightweight Angular/Ionic test shell, then run an Ionic/Angular build that carries the same version tag.
• Push the finished test-app artifact straight to LambdaTest, run an automated sanity check, and confirm the user can move back and forth between the Ionic and embedded Flutter views without glitches.
• Wrap every tool—Flutter, Ionic/Angular CLI, Node, Fastlane (or your preferred iOS helper), plus the LambdaTest runner—inside a single Linux-based Docker image so anyone can clone the repo, run docker run, and get identical results.
• Publish a Swagger-documented REST API (served on the container’s pre-assigned port) with two core endpoints:
– POST /build : trigger a fresh build
– GET /artifact/:version : download the exact test-app build by version
Authentication is via API Key header only.

An external Angular app will eventually call this service, bump its own dependency, and pull the newest build, much like it would grab a package from npm—so the versioning scheme needs to be consistent and machine-readable.

Deliverables
1. Dockerfile and supporting scripts that perform the entire pipeline on Linux.
2. Source code for the microservice exposing the Swagger-documented endpoints, including an OpenAPI spec file.
3. Automated test that spins up the container, triggers a build, retrieves the artifact, and asserts LambdaTest returned a pass.
4. Minimal usage guide describing environment variables (API key, LambdaTest creds, signing certificates, etc.) and typical curl examples for the two endpoints.

If you have previous experience chaining Flutter and Ionic in CI, plus a knack for clean Docker images and Swagger docs, this should be a straightforward build.