Know which version is running
Deployment configuration records the Dev and production state in Git history. The pipeline updates the deployed versions.
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.
A push to main starts the prepared pipeline. Its status shows how far your change has progressed.
Tests and checks run against your code. If a job fails, its log gives you a place to investigate.
The pipeline calculates the version and creates the Docker image or app build for your stack.
The build deploys automatically to Dev. Mobile test builds go to TestFlight or internal Play tests when the accounts are connected.
After trying the build, start the manual release job for production or submission to the stores.
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.
mp run-localDeployment configuration records the Dev and production state in Git history. The pipeline updates the deployed versions.
Manage and publish Docker images and supported packages in your project. You choose who can use them.
The status and job log show which step failed. A green pipeline still does not replace trying your application yourself.
MainPath maintains generated pipeline and environment files. Your values go in custom files; sensitive credentials go in managed secrets.
Web applications need the appropriate server or hosting connection before the pipeline can make their build available.
A successful build alone does not publish a production update. Start the manual release job after reviewing the result.
Start a MainPath project and follow your change from the first push to a reviewed release.
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.
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.
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.
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.