Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update sccache bucket #693

Merged
5 commits merged into from
Feb 14, 2023
Merged

Update sccache bucket #693

5 commits merged into from
Feb 14, 2023

Conversation

ajschmidt8
Copy link
Collaborator

This PR updates the sccache configuration settings to use a new bucket, rapids-sccache-east.

Unlike the previous rapids-sccache bucket, rapids-sccache-east resides in the same AWS region as the rest of our CI infrastructure (us-east-2).

This should result in faster, more reliable sccache connections and will also help keep our data transfer costs down.

Important Note: The changes from this sccache PR are required to use a bucket in us-east-2. These changes were incorporated in sccache v0.3.2, so you'll need that version or later (preferably the latest, v0.3.3). Please ensure that your CI images satisfy this constraint before merging this PR.

Additionally, this PR updates the SCCACHE_REGION to the region of the bucket. This value is not meant to be a variable.

This PR updates the `sccache` configuration settings to use a new bucket, `rapids-sccache-east`.

Unlike the previous `rapids-sccache` bucket, `rapids-sccache-east` resides in the same AWS region as the rest of our CI infrastructure (`us-east-2`).

This should result in faster, more reliable `sccache` connections and will also help keep our data transfer costs down.

**Important Note**: The changes from [this `sccache` PR](mozilla/sccache#1403) are required to use a bucket in `us-east-2`. These changes were incorporated in `sccache` `v0.3.2`, so you'll need that version or later (preferably the latest, `v0.3.3`). Please ensure that your CI images satisfy this constraint before merging this PR.

Additionally, this PR updates the `SCCACHE_REGION` to the region of the bucket. This value is not meant to be a variable.
@ajschmidt8 ajschmidt8 requested review from a team as code owners February 12, 2023 00:01
@ajschmidt8 ajschmidt8 added non-breaking Non-breaking change improvement Improvement to existing functionality labels Feb 12, 2023
Copy link
Contributor

@dagardner-nv dagardner-nv left a comment

Choose a reason for hiding this comment

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

LGTM, I checked, our images are using 0.3.1. I'll push up new images this morning.

@dagardner-nv
Copy link
Contributor

#699

Adopt updated CI runner with sccache 0.3.3 & merge branch-23.03 changes
@dagardner-nv dagardner-nv self-requested a review February 14, 2023 15:54
@dagardner-nv
Copy link
Contributor

/merge

@ghost ghost merged commit 981666d into branch-23.03 Feb 14, 2023
jjacobelli pushed a commit to jjacobelli/Morpheus that referenced this pull request Mar 7, 2023
This PR updates the `sccache` configuration settings to use a new bucket, `rapids-sccache-east`.

Unlike the previous `rapids-sccache` bucket, `rapids-sccache-east` resides in the same AWS region as the rest of our CI infrastructure (`us-east-2`).

This should result in faster, more reliable `sccache` connections and will also help keep our data transfer costs down.

**Important Note**: The changes from [this `sccache` PR](mozilla/sccache#1403) are required to use a bucket in `us-east-2`. These changes were incorporated in `sccache` `v0.3.2`, so you'll need that version or later (preferably the latest, `v0.3.3`). Please ensure that your CI images satisfy this constraint before merging this PR.

Additionally, this PR updates the `SCCACHE_REGION` to the region of the bucket. This value is not meant to be a variable.

Authors:
  - AJ Schmidt (https://github.com/ajschmidt8)
  - David Gardner (https://github.com/dagardner-nv)

Approvers:
  - David Gardner (https://github.com/dagardner-nv)

URL: nv-morpheus#693
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improvement to existing functionality non-breaking Non-breaking change
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants