-
Notifications
You must be signed in to change notification settings - Fork 50k
Build and store DevTools artifacts in Circle CI #17746
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
Build and store DevTools artifacts in Circle CI #17746
Conversation
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit cd76991:
|
threepointone
left a comment
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.
Preemptive stamp
5889930 to
1f5f2e5
Compare
|
I think Circle CI is confused. Looks like it re-ran part of the build commands without cleaning up, so now some things are failing b'c files are left over from previous runs. I used to have the option to clear cache and re-run but I don't see it anymore. |
aa577a8 to
756dfc9
Compare
756dfc9 to
cd76991
Compare
|
Yay Circle CI seems to have finally passed after the last round of changes. |
Hi Guys Your ideas appeal to me. Could you describe the detail of the ideas? |
Might as well leverage Circle CI to test our DevTools builds, and if we're doing that- we might as well store the artifacts as well. Maybe in the future, we should release DevTools directly from CI artifacts as well, like we do for NPM packages.
Let's see if these changes actually work... 😄