Skip to content

Build: Store storybook log when building sandboxes#24938

Closed
IanVS wants to merge 1 commit into
nextfrom
save-yarn-error-artifact
Closed

Build: Store storybook log when building sandboxes#24938
IanVS wants to merge 1 commit into
nextfrom
save-yarn-error-artifact

Conversation

@IanVS

@IanVS IanVS commented Nov 21, 2023

Copy link
Copy Markdown
Member

Closes #

What I did

Added storybook.log to circleci artifacts.

I have seen yarn errors in CI that I don't understand, and the output says to check this file for more details about the error. Ref: https://app.circleci.com/pipelines/github/storybookjs/storybook/64069/workflows/e4471bb3-a8b2-4bfd-8ec4-fa3a712be17d/jobs/597980/parallel-runs/2

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

  • stories
  • unit tests
  • integration tests
  • end-to-end tests

Manual testing

Check circleci to see if a log file is stored as an artifact in the create sandboxes step.

Documentation

  • Add or update documentation reflecting your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Checklist for Maintainers

  • When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts

  • Make sure this PR contains one of the labels below:

    Available labels
    • bug: Internal changes that fixes incorrect behavior.
    • maintenance: User-facing maintenance tasks.
    • dependencies: Upgrading (sometimes downgrading) dependencies.
    • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
    • cleanup: Minor cleanup style change. Will not show up in release changelog.
    • documentation: Documentation only changes. Will not show up in release changelog.
    • feature request: Introducing a new feature.
    • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
    • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

@IanVS IanVS added the build Internal-facing build tooling & test updates label Nov 21, 2023
@IanVS IanVS mentioned this pull request Nov 21, 2023
8 tasks
@IanVS IanVS added the ci:normal Run our default set of CI jobs (choose this for most PRs). label Nov 21, 2023
@IanVS

IanVS commented Nov 21, 2023

Copy link
Copy Markdown
Member Author

It looks like @ndelangen might be addressing this same issue a different way, by logging the output during CI: https://github.com/storybookjs/storybook/pull/24935/files#diff-f8bc096511bc0e2dc643d33307224f4d3fb354d2f9ecf5ec377c5b9eaca66e99R213

@IanVS

IanVS commented Nov 21, 2023

Copy link
Copy Markdown
Member Author

Doesn't seem to have worked, and I'm not sure where this file is actually placed on disk (probably the generated sandbox directory).

@IanVS IanVS closed this Nov 21, 2023
@kasperpeulen kasperpeulen deleted the save-yarn-error-artifact branch April 4, 2026 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Internal-facing build tooling & test updates ci:normal Run our default set of CI jobs (choose this for most PRs).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant