Remove README changes and update Makefile for Java 17/21 support

Author: szhu95

Makefile

@@ -1,35 +1,35 @@
-JENKINS_REMOTING_TAG := latest-jdk11
+JENKINS_REMOTING_TAG := 4.13.2-1-jdk11
 JOB := remoting-${JENKINS_REMOTING_TAG}
 CLEAN_JOB := clean-${CORE_TAG}
 
 # Default target builds Java 11 variant
-all: remoting-latest-jdk11 remoting-latest-jdk17 remoting-latest-jdk21
+all: remoting-4.13.2-1-jdk11 remoting-4.13.2-1-jdk17 remoting-4.13.2-1-jdk21
 
 clean: ${CLEAN_JOB}
-.PHONY: all clean ${JOB} ${CLEAN_JOB} remoting-latest-jdk11 remoting-latest-jdk17 remoting-latest-jdk21
+.PHONY: all clean ${JOB} ${CLEAN_JOB} remoting-4.13.2-1-jdk11 remoting-4.13.2-1-jdk17 remoting-4.13.2-1-jdk21
 
 ${JOB}: remoting-%: Dockerfile
 	docker build \
 	  --build-arg JENKINS_REMOTING_TAG=$* \
 	  --tag dwolla/jenkins-agent-core:$*-SNAPSHOT \
 	  .
 
-remoting-latest-jdk11: Dockerfile
+remoting-4.13.2-1-jdk11: Dockerfile
 	docker build \
-	  --build-arg JENKINS_REMOTING_TAG=latest-jdk11 \
-	  --tag dwolla/jenkins-agent-core:latest-jdk11-SNAPSHOT \
+	  --build-arg JENKINS_REMOTING_TAG=4.13.2-1-jdk11 \
+	  --tag dwolla/jenkins-agent-core:4.13.2-1-jdk11-SNAPSHOT \
 	  .
 
-remoting-latest-jdk17: Dockerfile
+remoting-4.13.2-1-jdk17: Dockerfile
 	docker build \
-	  --build-arg JENKINS_REMOTING_TAG=latest-jdk17 \
-	  --tag dwolla/jenkins-agent-core:latest-jdk17-SNAPSHOT \
+	  --build-arg JENKINS_REMOTING_TAG=4.13.2-1-jdk17 \
+	  --tag dwolla/jenkins-agent-core:4.13.2-1-jdk17-SNAPSHOT \
 	  .
 
-remoting-latest-jdk21: Dockerfile
+remoting-4.13.2-1-jdk21: Dockerfile
 	docker build \
-	  --build-arg JENKINS_REMOTING_TAG=latest-jdk21 \
-	  --tag dwolla/jenkins-agent-core:latest-jdk21-SNAPSHOT \
+	  --build-arg JENKINS_REMOTING_TAG=4.13.2-1-jdk21 \
+	  --tag dwolla/jenkins-agent-core:4.13.2-1-jdk21-SNAPSHOT \
 	  .
 
 ${CLEAN_JOB}: clean-%:

README.md

@@ -7,38 +7,3 @@ Docker images containing the Jenkins remoting JAR and necessary dependencies.
 GitHub Actions will build the Docker images for multiple supported architectures.
 
 To build locally, run `make all` or `make remoting-${TAG}` for one of the supported tags.
-
-## Privileged Token Support
-
-This agent supports both regular and privileged tokens for Jenkins authentication. The agent will automatically use a privileged token if provided, with fallback to a regular token.
-
-### Environment Variables
-
-- `JENKINS_PRIVILEGED_SECRET` - Privileged token (takes priority if set)
-- `JENKINS_SECRET` - Regular token (used if privileged token not provided)
-- `JENKINS_URL` - Jenkins controller URL (required)
-- `JENKINS_AGENT_NAME` - Agent name (optional)
-
-### Usage
-
-For privileged builds, provide the privileged token:
-
-```bash
-docker run -d \
-  -e JENKINS_URL=https://your-jenkins-server.com \
-  -e JENKINS_PRIVILEGED_SECRET=your-privileged-token \
-  -e JENKINS_AGENT_NAME=agent-name \
-  dwolla/jenkins-agent-core:4.13.2-1-jdk11-SNAPSHOT
-```
-
-For regular builds, use the standard token:
-
-```bash
-docker run -d \
-  -e JENKINS_URL=https://your-jenkins-server.com \
-  -e JENKINS_SECRET=your-regular-token \
-  -e JENKINS_AGENT_NAME=agent-name \
-  dwolla/jenkins-agent-core:4.13.2-1-jdk11-SNAPSHOT
-```
-
-**Note:** The agent uses the token provided at startup for the connection. To support both privileged and non-privileged builds, deploy separate agent instances with the appropriate tokens.