Your next updateA clear path to release

Your AI agent writes new features. MainPath prepares what follows: checking changes, creating builds and deploying to Dev. You make the decision to release to production.

Tests, builds and a preview are part of the prepared project workflow

From push to releaseOne step at a time

A push to main starts the prepared pipeline. Its status shows how far your change has progressed.

  1. Check the changes

    Tests and checks run against your code. If a job fails, its log gives you a place to investigate.

  2. Create the build

    The pipeline calculates the version and creates the Docker image or app build for your stack.

  3. Try it on Dev

    The build deploys automatically to Dev. Mobile test builds go to TestFlight or internal Play tests when the accounts are connected.

  4. Choose when to release

    After trying the build, start the manual release job for production or submission to the stores.

A pipeline job failed?Keep working on the code

Start with the failed job’s log. Run your project locally and investigate the cause with your AI agent. Once you have fixed it, a new push checks the next version.

  • Generated files such as .gitlab-ci.yml stay unchanged
  • Your environment values belong in the documented custom files
  • Arrange additional pipeline automation through MainPath configuration or support
mp run-local
Starts your project locally. Pipeline jobs and their logs are available in GitLab.

Keep the result within reachVersions and build outputs

Know which version is running

Deployment configuration records the Dev and production state in Git history. The pipeline updates the deployed versions.

Reuse your build outputs

Manage and publish Docker images and supported packages in your project. You choose who can use them.

Automation you can followDecisions stay with you

  • A starting point for errors

    The status and job log show which step failed. A green pipeline still does not replace trying your application yourself.

  • A place for configuration

    MainPath maintains generated pipeline and environment files. Your values go in custom files; sensitive credentials go in managed secrets.

  • Dev needs a target environment

    Web applications need the appropriate server or hosting connection before the pipeline can make their build available.

  • Production waits for your approval

    A successful build alone does not publish a production update. Start the manual release job after reviewing the result.

Your feature is builtGive it a reliable path forward

Start a MainPath project and follow your change from the first push to a reviewed release.

Questions about the pipeline flow

Do I need to write the pipeline myself?

No. MainPath creates an appropriate GitLab CI pipeline for supported projects. Which tests and checks are useful still depends on your application and its test code.

Can my AI agent edit .gitlab-ci.yml?

MainPath maintains and overwrites the generated .gitlab-ci.yml. Your agent should not change it, including when a job fails. Use the documented custom files for your environment values and discuss additional pipeline automation with support.

Configuration and custom files

Does every push go straight to production?

No. Changes on main are checked, built and distributed to Dev or mobile test channels. Production and store submission start through the manual release job. The relevant store still decides whether to approve an app.

What should I do when a pipeline fails?

Open the failed job in GitLab and check its log. Investigate the cause locally with your agent, fix the code and push again. If the cause remains unclear, send the pipeline link to support through the contact page.

Contact support

Thank you for your request

We have received your request and will get back to you as soon as possible.

Would you like to talk to us directly?

Choose a time here for an introductory call with Robin.

Open the calendar in a new tab