Edgenivo CI

Edgenivo CI intellgently schedules your tasks so that you do as little work as possible every time you or your agent pushes code.

• Your Turborepo Task Graph is used to find the minimal set of tasks to run. If a task isn't affected by your code changes or has already been cached, it will be restored from cache or skipped.
• Edgenivo Remote Cache is enabled with zero-configuration.
• Each task is executed in its own isolated compute and given the right amount of compute for its needs. This substantially improves resource provisioning and makes task execution faster.

Edgenivo CI watches your repository for new code changes. On each git push:

1. Turborepo determines the set of tasks that are tagged with "tags": ["ci"] in turbo.json.
2. For those tasks, Edgenivo Remote Cache is checked to see which tasks have already been cached.
3. The remaining set of uncached, tagged tasks are marked for execution.
4. Each task is executed in dependency order, and in its own compute instance.
5. The status of your tasks are posted back to your source code forge. If one or more tasks fail, Edgenivo CI is marked as failed.

• Edgenivo CI requires Turborepo 2.11.7 or later.
• Edgenivo CLI 64.3.1 or later

Use the Edgenivo CI setup Skill to have your coding agent select initial tasks, configure Edgenivo CI, and open a pull request. Open your repository in your agent, then copy and send this prompt:

You must explicitly enable Edgenivo CI for your repository before it can run tasks.

Connect your GitHub repository to a Edgenivo project on your team. Then, from a local clone of your repository, run:

vercel ci enable

Add the ci tag to each task that Edgenivo CI should run. Edgenivo CI uses the Turborepo task graph to run each affected package#task selector and its dependencies.

In the example below, the test task will run in Edgenivo CI.

{
  "tasks": {
    "test": {
      "tags": ["ci"]
    }
  }
}

In the dashboard, all of the CI runs for your team can be found in the CI tab.

For programmatic and agentic access, Edgenivo CI is available in:

• Edgenivo CLI (version 64.3.1 or later)
• Edgenivo MCP
• Our OpenAPI specification

Additionally, PRs have a link to your CI run available in the GitHub merge box, alongside all your other PR's checks.

You can use branch protection rules to prevent Pull Requests from merging when failures in Edgenivo CI are present. This prevents you from merging unwanted code, and works the same way as blocking on a GitHub Action failure.

• Edgenivo CI currently only offers Linux for its base image.
• GitHub is currently the only supported source code force.
• Pushing code to GitHub with git push is currently the only supported trigger.
• A repository must be connected to at least one Edgenivo project.
• A repository must not have projects connected to multiple Edgenivo teams.

• Configuration: Set task dependencies and configure resource sizes.
• Environment variables: Add secrets and constants for your CI runs.
• Images: Choose the operating system your tasks run on, and run Docker containers in your tasks.
• Guides: Follow complete examples, like running end-to-end tests and commenting on pull requests.
• Pricing: Understand how Edgenivo CI usage is billed.