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

fix(ci): further consolidate NODE_OPTIONS #12217

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

david-leifker
Copy link
Collaborator

Prevent having to track down and modify memory settings in multiple places for NODE_OPTIONS

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
  • For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@github-actions github-actions bot added product PR or Issue related to the DataHub UI/UX devops PR or Issue related to DataHub backend & deployment labels Dec 23, 2024
@datahub-cyborg datahub-cyborg bot added the needs-review Label for PRs that need review from a maintainer. label Dec 23, 2024
@david-leifker david-leifker force-pushed the node-options-consilidation branch from 985476a to 44566ab Compare December 24, 2024 00:15
@david-leifker david-leifker force-pushed the node-options-consilidation branch from 44566ab to 2390b28 Compare December 24, 2024 00:46
@david-leifker david-leifker force-pushed the node-options-consilidation branch from 2390b28 to 79088ac Compare December 24, 2024 01:11
"analyze": "NODE_OPTIONS='--max-old-space-size=5120 --openssl-legacy-provider' source-map-explorer 'dist/assets/*.js'",
"start": "NODE_OPTIONS='--max-old-space-size=5120 --openssl-legacy-provider' yarn run generate && NODE_OPTIONS='--max-old-space-size=5120 --openssl-legacy-provider' vite",
"ec2-dev": "NODE_OPTIONS='--max-old-space-size=5120 --openssl-legacy-provider' yarn run generate && CI=true NODE_OPTIONS='--max-old-space-size=5120 --openssl-legacy-provider' vite",
"build": "NODE_OPTIONS='--max-old-space-size=5120 --openssl-legacy-provider' yarn run generate && CI=false NODE_OPTIONS='--max-old-space-size=5120 --openssl-legacy-provider' vite build",
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 only be necessary on the vite build step

Copy link
Collaborator Author

@david-leifker david-leifker Dec 24, 2024

Choose a reason for hiding this comment

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

Removed it from several of them. The storybook build causes OOM in Saas. Enabling coverage on the test also triggers OOM, so more then just vite build is likely warranted.

@david-leifker david-leifker force-pushed the node-options-consilidation branch from 79088ac to dc0d6bb Compare December 24, 2024 01:16
@datahub-cyborg datahub-cyborg bot added pending-submitter-merge and removed needs-review Label for PRs that need review from a maintainer. labels Dec 24, 2024
@david-leifker david-leifker force-pushed the node-options-consilidation branch from dc0d6bb to a80d6a5 Compare December 24, 2024 01:59
@@ -79,7 +79,7 @@ task yarnServe(type: YarnTask, dependsOn: [yarnInstall, yarnGenerate]) {

task yarnTest(type: YarnTask, dependsOn: [yarnInstall, yarnGenerate]) {
// Explicitly runs in non-watch mode.
args = ['run', 'test', 'run']
args = ['run', project.hasProperty('withCoverage') ? 'test-coverage' : 'test', 'run']
Copy link
Collaborator

Choose a reason for hiding this comment

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

Where is this property being set? We would want the coverage to be generated when gradle runs the test task (like all other projects).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops PR or Issue related to DataHub backend & deployment pending-submitter-merge product PR or Issue related to the DataHub UI/UX
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants