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

ci: Updated security agent workflow to use large runners when available #2271

Merged
merged 4 commits into from
Jun 12, 2024

Conversation

bizob2828
Copy link
Member

Fixes issues from #2270

jsumners-nr
jsumners-nr previously approved these changes Jun 12, 2024
Copy link
Contributor

@jsumners-nr jsumners-nr left a comment

Choose a reason for hiding this comment

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

Dolla dolla bills!

@bizob2828 bizob2828 added the dev:automation Indicates CI automation label Jun 12, 2024
@@ -82,6 +82,7 @@ jobs:
run: TEST_CHILD_TIMEOUT=600000 npm run versioned:security
env:
VERSIONED_MODE: --${{ inputs.mode || 'major' }}
JOBS: 4 # 2 per CPU seems to be the sweet spot in GHA (July 2022)
# Run more jobs when using larger runner, otherwise 2 per CPU seems to be the sweet spot in GHA default runners(July 2022)
JOBS: ${{ vars.NR_RUNNER && 16 || 4 }}
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm surprised the GHA parser is this robust.

@bizob2828
Copy link
Member Author

Ran with larger runner and 4 jobs and it passed here. Waiting on the 16 jobs run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev:automation Indicates CI automation
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants