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

Run all smoke tests with the static build #2609

Merged
merged 6 commits into from
Feb 23, 2022
Merged

Run all smoke tests with the static build #2609

merged 6 commits into from
Feb 23, 2022

Conversation

matthewp
Copy link
Contributor

Changes

  • Test change only

Testing

All of the examples that are smoke tested are also run with `--experimental-static-build flag.

Docs

Test only

@changeset-bot
Copy link

changeset-bot bot commented Feb 17, 2022

⚠️ No Changeset found

Latest commit: 79f9d29

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions github-actions bot added the pkg: example Related to an example package (scope) label Feb 17, 2022
@natemoo-re
Copy link
Member

This is the same bug tripping me up in https://github.com/withastro/astro/runs/5252193656. Seems like the astro.build site is using a relative path or Astro.resolve or something?

@matthewp
Copy link
Contributor Author

This PR isn't expected to pass until astro.build converts to the static build.

@natemoo-re
Copy link
Member

Static build support merged in withastro/astro.build#29

@matthewp
Copy link
Contributor Author

Let's hold off on merge until the release, just in the off-chance this is flakey I don't want it holding up other PRs.

Copy link
Member

@FredKSchott FredKSchott left a comment

Choose a reason for hiding this comment

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

Since --experimental-static-build changes behavior, we should probably move this flag into the package.json of each example. ie:

-    "build": "astro build",
+    "build": "astro build --experimental-static-build",

These get run directly by users via astro.new, so I'd be worried about them passing CI but failing when users actually go to run them. If the package.json were updated instead, our CI can trust that yarn build does the right thing for each project.

@matthewp
Copy link
Contributor Author

I don't think we should opt users into an experimental flag on all new projects. The goal of this PR is to ensure that the the experimental flag works on all of the examples. This runs both builds, so we know that both work with yarn build, and users are getting the stable version on new projects.

Copy link
Member

@FredKSchott FredKSchott left a comment

Choose a reason for hiding this comment

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

Ah, got it. Makes sense!

@matthewp matthewp merged commit 2ad88a9 into main Feb 23, 2022
@matthewp matthewp deleted the smoke-sb branch February 23, 2022 13:41
SiriousHunter pushed a commit to SiriousHunter/astro that referenced this pull request Feb 3, 2023
* Run all smoke tests with the static build

* Use a direct relative path

* Always use the static build

* Use a path that works in both static and regualr build

* Always download the zip

* astro.build only needs to run once
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pkg: example Related to an example package (scope)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants