docker inbound agent
Basic Information
This repository housed a Docker image project that provided a Jenkins inbound agent capable of connecting back to a Jenkins controller using TCP or WebSocket protocols. The primary purpose was to supply a containerized agent that initiates a connection to the Jenkins master rather than being started by the controller, enabling agents to run in environments where inbound connectivity is required. The repo is archived and read-only as of January 21, 2024. The project has been marked deprecated and integrated into a consolidated docker-agent offering, so this repository mainly remains as historical documentation and a record of the inbound-agent image and its intent.
Links
Stars
479
Github Repository
App Details
Features
Provided a Docker image for a Jenkins inbound agent with support for TCP and WebSocket connection modes. Designed to run as a containerized worker that initiates the connection to the Jenkins controller. Intended to simplify running ephemeral or network-restricted agents by letting the agent open the channel inbound to the master. The repository was archived and marked deprecated, with functionality merged into a unified docker-agent project. The tree references a main README and minimal project metadata; no active updates are being made in this archived repository.
Use Cases
The image was useful for teams needing containerized Jenkins workers that can reach the controller from restricted networks or cloud environments where the controller cannot directly open connections to agents. It reduced the operational burden of provisioning and maintaining long-lived SSH or other outbound agent mechanisms by allowing agents to initiate secure TCP or WebSocket sessions. For current usage, the repository serves as a historical reference and signals that users should migrate to the integrated docker-agent project which now contains the maintained implementation.
-
$$$$ -
$$$$