Skip to content

GCLOUD_TESTS_BUCKET_NAME not needed anymore for storage regression testing #270

Description

@silvolu
No description provided.

Activity

  1. stephenplusplus commented on Oct 30, 2014

    @stephenplusplus
    Contributor

    I noticed the same thing today-- I can get this after #264 goes 👍

  2. ryanseys commented on Nov 2, 2014

    @ryanseys
    Contributor

    Why not? Are we using a default predictable name now?

  3. stephenplusplus commented on Nov 2, 2014

    @stephenplusplus
    Contributor

    Before the Storage api refactor, there wasn't a way to create a bucket. Now that we can, we don't need to have the dev make their own. We will just maintain one and trash it when we're done.

  4. ryanseys commented on Nov 2, 2014

    @ryanseys
    Contributor

    Ah, okay. So this will use a bucket name as something like 'gcloud-regtest-{{uuid}}' instead? We'll also need to ensure that it doesn't conflict with an already existing bucket but the added uuid should handle that.

  5. stephenplusplus commented on Nov 3, 2014

    @stephenplusplus
    Contributor

    Sgtm. Working on this now.

  6. added 2 commits that reference this issue on Nov 3, 2014
    7464e17
    a049907
  7. added this to the Storage Stable milestone on Feb 2, 2015
  8. added a commit that references this issue on Oct 11, 2022
  9. 34 remaining items

  10. added a commit that references this issue on Feb 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

🚨This issue needs some love.api: storageIssues related to the Cloud Storage API.triage meI really want to be triaged.

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions