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

enforce base package to build first #118

Merged
merged 1 commit into from
Oct 5, 2023
Merged

enforce base package to build first #118

merged 1 commit into from
Oct 5, 2023

Conversation

MCarlomagno
Copy link
Member

pnpm nx-build-test-skip-cache command was failing due to parallel building, some packages depend on base to build properly, so I changed secuential builds, this is slower but seems to be necesary.

cc @tirumerla

@changeset-bot
Copy link

changeset-bot bot commented Oct 5, 2023

⚠️ No Changeset found

Latest commit: e986ba7

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

@@ -34,7 +34,7 @@
"nx-build-test-skip-cache": "pnpm run build-test --skip-nx-cache",
"nx-test-skip-cache": "pnpm run test --skip-nx-cache",
"build": "nx run-many -t build --parallel=1",
"build-test": "nx run-many -t style,build,test",
"build-test": "nx run-many -t style,build,test --projects=@openzeppelin/defender-base-client,* --parallel=false",
Copy link
Member Author

Choose a reason for hiding this comment

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

This is the relevant change, the rest are just pre-commit format changes

Copy link
Collaborator

Choose a reason for hiding this comment

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

This should not be necessary since parallel=1 should still run sequentially. Is it not the case?

Copy link
Member Author

Choose a reason for hiding this comment

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

Doesn't seem to work :/ it tries to run notification-channel:build before base:build.

By the docs it seems tha the way to run secuentially is by setting parallel=false

Screenshot 2023-10-05 at 15 08 17

Copy link
Collaborator

Choose a reason for hiding this comment

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

Interesting. Sounds good. Thanks

Copy link
Collaborator

@tirumerla tirumerla left a comment

Choose a reason for hiding this comment

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

lgtm

@MCarlomagno MCarlomagno merged commit e19128f into main Oct 5, 2023
4 checks passed
@MCarlomagno MCarlomagno deleted the fix-build-order branch October 5, 2023 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants