Skip to content

Improve components infrastructure #12024

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

Closed
wants to merge 15 commits into from
Closed

Improve components infrastructure #12024

wants to merge 15 commits into from

Conversation

JunTaoLuo
Copy link
Contributor

@JunTaoLuo JunTaoLuo commented Jul 9, 2019

Addresses #12030

A few of the workflows I'm trying to improve:

  • Build blazor.*.js in CI; don't commit the artifacts #11592 Stop checking in JS artifacts from Web.JS in Components and compile the artifacts at build time. I need to check that relying on yarn is compatible with source build
  • Able to trigger builds of Web.JS from depending projects
  • ./build.cmd in Components dir should succeed if yarn is installed

@rynowak
Copy link
Member

rynowak commented Jul 9, 2019

Can I get a cool description? What do you expect to be fixed/improved by this change?

@JunTaoLuo
Copy link
Contributor Author

Haven't decided on the full extent of what I will address in this PR and how to break it up yet. Will add details as I go.

@rynowak
Copy link
Member

rynowak commented Jul 10, 2019

ok dope. Looking forward to more details.

@analogrelay analogrelay added area-blazor Includes: Blazor, Razor Components area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework labels Jul 10, 2019
@JunTaoLuo
Copy link
Contributor Author

I'm going to limit this change to fix the common workflows in Components only and will address other sub-areas (native, templates, etc) separately. I still need to test some more scenarios, pack, test, building when yarn isn't installed, etc, so expect a few more small changes.

@@ -11,7 +11,7 @@
Importance="High"
Text="Prerequisites were not enforced at build time. Running Yarn or the E2E tests might fail as a result. Check /src/Shared/E2ETesting/Readme.md for instructions." />

<Yarn Command="install --mutex network" />
<Yarn Command="install --mutex network" Condition="'$(EnforceE2ETestPrerequisites)' == 'true'"/>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

WIP, I think this will break some dev workflows. Don't check this in yet.

@JunTaoLuo JunTaoLuo closed this Jul 13, 2019
@JunTaoLuo JunTaoLuo reopened this Jul 13, 2019
@JunTaoLuo JunTaoLuo force-pushed the johluo/components branch 3 times, most recently from b926cf5 to 7c73b91 Compare July 13, 2019 01:18
@JunTaoLuo
Copy link
Contributor Author

I'm going to create another PR, I have no idea why the CI isn't building this branch anymore.

@JunTaoLuo JunTaoLuo closed this Jul 13, 2019
@JunTaoLuo JunTaoLuo deleted the johluo/components branch May 22, 2020 03:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants