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

Configure agent-node usage based on jenkins instance type #509

Open
Tracked by #382
Divyaasm opened this issue Nov 19, 2024 · 0 comments
Open
Tracked by #382

Configure agent-node usage based on jenkins instance type #509

Divyaasm opened this issue Nov 19, 2024 · 0 comments
Assignees

Comments

@Divyaasm
Copy link
Collaborator

Divyaasm commented Nov 19, 2024

Current agent node setup and initialization is confined to use all the supported agent types while creating a jenkins instance as part of stack creation.

  • Reorganize the agent node types into three different types by separating into agent types used by release/test/build workflows, benchmark test-workflows and gradle check workflows.
  • We should be able bring up a requested jenkins instance type as mentioned above, only with the necessary agent nodes required by the workflows using it.
@github-actions github-actions bot added the untriaged Issues that have not yet been triaged label Nov 19, 2024
@Divyaasm Divyaasm removed the untriaged Issues that have not yet been triaged label Nov 19, 2024
@Divyaasm Divyaasm moved this from 🆕 New to 🏗 In progress in Engineering Effectiveness Board Nov 19, 2024
@Divyaasm Divyaasm self-assigned this Nov 19, 2024
@Divyaasm Divyaasm moved this from 🏗 In progress to 👀 In Review in Engineering Effectiveness Board Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 👀 In Review
Development

No branches or pull requests

1 participant