AWS CDK Jenkins inbound agent for cloud deployment.
1.2K
This is an image for Jenkins agents using TCP or WebSockets to establish inbound connection to the Jenkins master. Linux agent is available only.
To run a Docker container
Linux agent:
docker run --init gclim/aws-cdk-inbound-agent -url http://jenkins-server:port <secret> <agent name>
Note: --init is necessary for correct subprocesses handling (zombie reaping)
To run a Docker container with Work Directory
Linux agent:
docker run --init gclim/aws-cdk-inbound-agent -url http://jenkins-server:port -workDir=/home/jenkins/agent <secret> <agent name>
Optional environment variables:
JENKINS_URL: url for the Jenkins server, can be used as a replacement to -url option, or to set alternate jenkins URLJENKINS_TUNNEL: (HOST:PORT) connect to this agent host and port instead of Jenkins server, assuming this one do route TCP traffic to Jenkins master. Useful when when Jenkins runs behind a load balancer, reverse proxy, etc.JENKINS_SECRET: agent secret, if not set as an argumentJENKINS_AGENT_NAME: agent name, if not set as an argumentJENKINS_AGENT_WORKDIR: agent work directory, if not set by optional parameter -workDirJENKINS_WEB_SOCKET: true if the connection should be made via WebSocket rather than TCPThis image only supports the JNLP4-connect protocol. As a result, Jenkins versions prior to 2.32 are no longer supported.
Make sure your ECS container agent is updated before running. Older versions do not properly handle the entryPoint parameter. See the entryPoint definition for more information.
Content type
Image
Digest
Size
178.9 MB
Last updated
over 6 years ago
docker pull gclim/aws-cdk-inbound-agent