Skip to content

Compatibility and limits

Avrea CI uses GitHub Actions workflow syntax, with the support described below. Copying the YAML is the starting point; workflows that depend on GitHub-hosted services may need changes.

FeatureAvrea CI support
RunnersAvrea Linux, macOS, and Windows labels, including supported Linux ARM sizes.
StepsShell commands, JavaScript actions, composite actions, and Docker actions on Linux.
Dependenciesneeds, job and step conditions, step outputs, and job outputs.
Reusable workflowsLocal and authorized cross-repository calls in push workflows, including nested calls and matrices.
MatricesStatic and dynamic matrices, include, exclude, fail-fast, and max-parallel.
ConcurrencyWorkflow and job groups, cancellation of older work, and queue: max.
ContainersLinux job containers and service containers.
TriggersBranch and tag pushes, pull requests, and manual workflow_dispatch.
ConfigurationAvrea secrets and variables in eligible push and manual workflows, including named variables in scheduling fields.
RerunsCompleted workflows, failed jobs, or selected jobs and their downstream dependents.
Feature or dependencyLimit and next step
GitHub-hosted and self-hosted labelsEvery runner label must resolve to an Avrea Linux, macOS, or Windows runner. runs-on runner-group objects are unsupported.
Reusable workflowsPush runs only. Private cross-repository sources require the same GitHub App installation and explicit sharing; public sources require approved access. Review call restrictions.
Other eventsschedule, workflow_run, repository_dispatch, pull_request_target, merge_group, and other events outside the supported trigger set do not start Avrea CI runs. Keep those automations on GitHub Actions.
GitHub secrets and variablesNot imported. Configure values in Avrea and review event eligibility.
GitHub tokenNo automatic general-purpose GITHUB_TOKEN. Standard checkout receives repository read access, but that does not authorize GitHub API calls or pushes.
Token permissions and OIDCpermissions does not mint a GitHub token or GitHub Actions OIDC identity. Review publishing, cloud authentication, attestations, and other token-dependent actions.
Protected environmentsenvironment selects a configuration scope. GitHub approvals, wait timers, and deployment protection rules are not enforced by Avrea CI.
Fork pull requestsPublic target repositories require approval tied to the pull request event and exact head/base commits. Private target repositories are unsupported. Approved fork runs have no managed configuration or access to Avrea cache services. When persistent data disks are enabled, the default disk policy gives these runs a disposable copy of the published disk: they can read its contents, but their writes are discarded.
GitHub run identityAvrea CI has its own run IDs. Do not construct GitHub Actions run URLs or assume github.run_id is a numeric GitHub run ID.
ArtifactsUse Avrea artifact actions when their release prerequisites are satisfied. Artifacts stored in GitHub are not automatically available in Avrea.
CacheUse avrea-com/cache@v1 on updated Avrea runners. Review cache event support and scope before migrating.
Persistent storagePersistent data disks are supported when enabled for the repository. Saved Linux runner root filesystems require separate enablement through support. Review fork restrictions.
Cross-system concurrencyIdentically named groups in Avrea CI and GitHub Actions are independent. Keep deployments and publishing active in only one system during migration.

Third-party actions can depend on GitHub APIs even when their YAML is accepted. Test those actions with the intended event and credentials before making Avrea CI checks required.

Use avrea-com/cache@v1 to restore and save reusable job outputs. The cache action guide covers migration from actions/cache, examples, and runner requirements.

Avrea CI supports the Git, build, and package caches configured for the repository. Repository settings control which caches a job can access. For the GitHub Actions cache protocol, push and manual jobs on branches can read their branch and the default branch's caches, and write to their own branch. That cache integration is disabled for tag and pull request jobs. For fork runs, also review the fork restrictions.

For Linux job containers and Docker actions, cache setup also depends on the image. You may need explicit configuration for Gradle, Bazel, package managers, and ccache.

Check cache configuration and validate cache restore/save behavior for each event you use. Do not assume a cache hit is required for a workflow to succeed.

ResourceLimit
Workflow files64 directly inside .avrea/workflows/; .yml or .yaml.
One workflow file1 MiB.
Expanded jobs256 across the whole run, including matrix cells, reusable calls, and their child jobs.
Reusable workflow nestingAt most four nested calls; recursive calls are unsupported.
Expanded workflow definition8 MiB after expanding matrices and reusable workflows. Repeated step definitions also contribute to this limit.
Concurrent jobs in one runDefault cap of 10; runner capacity and organization limits also apply.
Run deadlineDefault 24 hours from creation, including time spent waiting.
Job timeoutDefault 360 minutes; set timeout-minutes per job. The overall run deadline still applies.
Manual inputs25 inputs and 65,535 characters of serialized input data.
Concurrency group name1,024 UTF-8 bytes.
queue: max100 pending entries per concurrency group.
Secret or variable value48 KiB.
Configuration references100 per job; 1,000 across expanded jobs in a run.

Run capacity and deadline defaults can differ by service configuration. Contact support@avrea.com if a limit prevents your workflow from running.

Invalid YAML and unsupported workflow features can fail a run before any VM starts. Trigger filtering, an unavailable pull request merge, and a repository that is not enabled can instead prevent a run from being created. See troubleshooting.