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

Jenkins Docker based agents. #312

Open
amalkuriakose opened this issue Sep 5, 2024 · 2 comments
Open

Jenkins Docker based agents. #312

amalkuriakose opened this issue Sep 5, 2024 · 2 comments

Comments

@amalkuriakose
Copy link

I understand that the Docker agent approach involves running Jenkins agents as Docker containers. This offers flexibility and scalability, as containers can be dynamically created and destroyed based on demand. However, running multiple containers on a single node can lead to resource contention, potentially overloading the node, right? How can we overcome this?

@mohammadsyed397
Copy link

To manage resource contention when running multiple Jenkins agents as Docker containers on a single node, you can set resource limits for CPU and memory using Docker's flags, implement dynamic scaling with orchestration tools like Kubernetes, and monitor resource usage with tools like Prometheus. Additionally, optimize job configurations to reduce resource consumption, utilize Jenkins' queue management features to control job concurrency, and consider separating resource-intensive jobs onto dedicated nodes. By combining these strategies, you can ensure efficient resource utilization and maintain optimal performance.

@mohammadsyed397
Copy link

correct me if i am wrong

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

No branches or pull requests

2 participants