Skip to content

Jenkins Docker based agents. #312

Open
@amalkuriakose

Description

@amalkuriakose

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions