Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
liujiuri
engine
提交
075eae59
E
engine
项目概览
liujiuri
/
engine
与 Fork 源项目一致
从无法访问的项目Fork
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
E
engine
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
未验证
提交
075eae59
编写于
11月 07, 2019
作者:
C
Christopher Fujino
提交者:
GitHub
11月 07, 2019
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Switch to Cirrus Dockerfile as CI (#13440)
上级
6fd58edd
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
20 addition
and
11 deletion
+20
-11
.cirrus.yml
.cirrus.yml
+8
-6
ci/docker/build/README.md
ci/docker/build/README.md
+12
-5
未找到文件。
.cirrus.yml
浏览文件 @
075eae59
...
...
@@ -3,13 +3,15 @@ gcp_credentials: ENCRYPTED[987a78af29b91ce8489594c9ab3fec21845bbe5ba68294b8f6def
# LINUX
task
:
gke_container
:
image
:
gcr.io/flutter-cirrus/build-engine-image:latest
cluster_name
:
build-32-cluster
zone
:
us-central1-a
namespace
:
default
cpu
:
30
# can't use all 30-cores; system pods needs cores too
memory
:
100Gb
# similarly, can't use all 100Gb memory
dockerfile
:
"
ci/docker/build/Dockerfile"
builder_image_name
:
docker-builder
# gce vm image
cluster_name
:
build-32-cluster
zone
:
us-central1-a
namespace
:
default
cpu
:
30
# can't use all 30-cores; system pods needs cores too
memory
:
100Gb
# similarly, can't use all 100Gb memory
env
:
CIRRUS_DOCKER_CONTEXT
:
"
ci/docker/build"
CIRRUS_WORKING_DIR
:
"
/tmp/github_repo"
ENGINE_PATH
:
"
/tmp/clean_engine"
DEPOT_TOOLS
:
"
/tmp/depot_tools"
...
...
ci/docker/build/README.md
浏览文件 @
075eae59
...
...
@@ -4,9 +4,16 @@ building flutter/engine in our CI system (currently [Cirrus](cirrus-ci.org)).
In order to run the scripts, you have to setup
`docker`
and
`gcloud`
. Please
refer to internal doc go/installdocker for how to setup
`docker`
on gLinux.
After setup,
*
edit
`Dockerfile`
to change how the container image is built.
*
run
`./build_docker.sh`
to build the container image.
*
run
`./push_docker.sh`
to push the image to google cloud registry. This will
affect our CI tests.
Cirrus will build (and cache) a Docker image based on this
`Dockerfile`
for
Linux tasks using its
[
Dockerfile as CI
](
https://cirrus-ci.org/guide/docker-builder-vm/
)
feature.
Any change to the
`Dockerfile`
will cause a new task to be triggered to build
and tag a new version of the Docker image which will be a dependency of the
other Linux tasks. This task will instantiate a new GCP VM based on the image
specified in the
`.cirrus.yml`
`builder_image_name`
field.
To test changes to the Linux
`Dockerfile`
, create a PR with the changes, and
Cirrus will attempt to build a new image.
To debug locally, you can build an image with
`./build_docker.sh`
, but pushing
to the registry is no longer necessary.
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录