-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
release-23.1: roachtest: codify longer ttl external storage buckets #111086
release-23.1: roachtest: codify longer ttl external storage buckets #111086
Conversation
Thanks for opening a backport. Please check the backport criteria before merging:
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
Add a brief release justification to the body of your PR to justify this backport. Some other things to consider:
|
f9febc4
to
fc9c6b2
Compare
pkg/testutils/backup.go
Outdated
// bucket. In private test runs, the name of the bucket is passed through an | ||
// environment variable. | ||
func BackupTestingBucket() string { | ||
return envutil.EnvOrDefaultString(backupTestingBucketEnvVar, defaultBackupBucket) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably better to have this code be exactly the same as master. Also EnvOrDefaultString
is for internal (COCKROACH_*
) vars only, I think this will panic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hrm. the linter was barking at me for not using envutil.... lemme figure out how to quiet the linter
fc9c6b2
to
bbd0653
Compare
Previously, the only codified external buckets for roachtests to back up to was the `cockroachdb-backup-testing` buckets in s3 and gcs which each had a ttl of 1 day. This low ttl is not suitable for roachtests that produce backups that the test failure investigator may want to inspect. This patch codifies the new `cockroachdb-backup-testing-long-ttl` buckets in s3 and gcs, which currently have a ttl of 20 days, the same ttl that team city artifacts have. This patch also points the c2c, backup-restore/mixed-version, and disagg-rebalance roachtests to use these new buckets. Note this PR only points roachtests that run in public TC environments to the new buckets. A future PR will set the BACKUP_TESTING_BUCKET_LONG_TTL env var for private roacttests to a new bucket with a longer ttl. Epic: none Release note: none
bbd0653
to
1537d25
Compare
Backport of #110288
Previously, the only codified external buckets for roachtests to back up to was the
cockroachdb-backup-testing
buckets in s3 and gcs which each had a ttl of 1 day. This low ttl is not suitable for roachtests that produce backups that the test failure investigator may want to inspect. This patch codifies the newcockroachdb-backup-testing-long-ttl
buckets in s3 and gcs, which currently have a ttl of 20 days, the same ttl that team city artifacts have.This patch also points the c2c, backup-restore/mixed-version, and disagg-rebalance roachtests to use these new buckets.
Note this PR only points roachtests that run in public TC environments to the new buckets. A future PR will set the BACKUP_TESTING_BUCKET_LONG_TTL env var for private roacttests to a new bucket with a longer ttl.
Epic: none
Release note: none
Release justification: test only change