fcb54add41
Bumps ubuntu from `b795f8e` to `db8bf6f`. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> |
||
|---|---|---|
| .. | ||
| docker_linux | ||
| mac | ||
| README.md | ||
This directory includes scripts and tools for setting up Flutter's continuous integration environments.
Cirrus Linux
Flutter's Linux tasks run on a custom Docker image. The Dockerfile for this
image can be found at /dev/ci/docker_linux/Dockerfile.
On each new change to this Dockerfile, Cirrus will build a new version of
the Docker image as a dependency to any Linux tests. It is no longer necessary
to manually build and push the Docker image locally.
There are some factors external to the actual Dockerfile that would
necessitate rebuilding the Docker image, such as upstream code changes, (Linux
distribution) repository updates or a file that gets COPYied into the image
changing. In this case, a trivial Dockerfile change (such as a comment)
would invalidate the cache and trigger a rebuild.