Skip to content

docs and docs-verify create large caches #102

@NEOatNHNG

Description

@NEOatNHNG

Description

The docs and docs-verify workflows create a huge cache (10GB).

Image

Analysis results

Is there a reason not to use the capabilities of the setup-bazel action for most of the caches and only use the separate cache for the sphinx content?

Solution

No response

Error Occurrence Rate

None

How to reproduce

No response

Supporting Information

No response

Classification

Minor

First Affected Release

not released (main)

Last Affected Release

not released (main)

Expected Fixed Release

before release (main)

Category

  • Safety Relevant
  • Security Relevant

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions