Skip to content

ci: save a few GB disk space#10669

Merged
mattklein123 merged 3 commits intoenvoyproxy:masterfrom
lizan:ci_debug
Apr 6, 2020
Merged

ci: save a few GB disk space#10669
mattklein123 merged 3 commits intoenvoyproxy:masterfrom
lizan:ci_debug

Conversation

@lizan
Copy link
Member

@lizan lizan commented Apr 6, 2020

Signed-off-by: Lizan Zhou lizan@tetrate.io

Signed-off-by: Lizan Zhou <lizan@tetrate.io>
@lizan lizan requested review from mattklein123 and tonya11en April 6, 2020 21:03
ci/do_ci.sh Outdated
tar czf "${ENVOY_BUILD_DIR}"/envoy_binary.tar.gz -C "${ENVOY_SRCDIR}" build_"$1" build_"$1"_stripped

# Remove binaries to save space
rm -rf "${ENVOY_SRCDIR}"/build_"$1" "${ENVOY_SRCDIR}"/build_"$1"_stripped "${ENVOY_DELIVERY_DIR}"/envoy
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @tonya11en I guess this might break your use case when you added cp_binary_for_outside_access

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm yeah not sure why this was added. @tonya11en @LisaLudique can one of you take a look and see if we use this at Lyft somehow?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I'm confused. Why would this break it? We are deleting after the copy which seems OK?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh I see. You are deleting what we already copied. Yeah I'm sure this is going to break something. Can you maybe guard this with an env var and then just set it for CI?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Or if we decide that we don't want the copy we should just delete cp_binary_for_outside_access() entirely.

Copy link
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, one small comment comment. Also, aren't we going to pretty quickly come up against the size limit again? Do we need to ask AZP about larger disk allocations?

ENVOY_DOCKER_BUILD_DIR: $(Build.StagingDirectory)
ENVOY_RBE: "true"
BAZEL_BUILD_EXTRA_OPTIONS: "--config=remote-ci --jobs=$(RbeJobs) --curses=no"
BAZEL_BUILD_EXTRA_OPTIONS: "--config=remote-ci --jobs=$(RbeJobs) --curses=no --experimental_repository_cache_hardlinks"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a comment on what this does and why we set it?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@mattklein123 mattklein123 self-assigned this Apr 6, 2020
Signed-off-by: Lizan Zhou <lizan@tetrate.io>
@lizan
Copy link
Member Author

lizan commented Apr 6, 2020

Thanks, one small comment comment. Also, aren't we going to pretty quickly come up against the size limit again? Do we need to ask AZP about larger disk allocations?

Yes we should ask AZP likely. Though it won't be quickly against the size limit again. We run all test in RBE which is not as disk constrained as in AZP (unless it prints huge logs that we download to AZP). The most disk consuming part is build-tools, i.e. our build image and bazel downloaded Go/Java SDK etc.

Signed-off-by: Lizan Zhou <lizan@tetrate.io>
Copy link
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@mattklein123
Copy link
Member

Going to force merge this since release passed and we can unwedge folks.

@mattklein123 mattklein123 merged commit a85f8ec into envoyproxy:master Apr 6, 2020
@lizan lizan deleted the ci_debug branch April 6, 2020 22:17
lizan added a commit that referenced this pull request May 5, 2020
Signed-off-by: Lizan Zhou <lizan@tetrate.io>
lizan added a commit that referenced this pull request May 5, 2020
Signed-off-by: Lizan Zhou <lizan@tetrate.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants