docs(ci): warn against redeploying an old controller app from the agent compose

ci/jenkins/docker-compose.yml used to define the Jenkins controller and now
defines only the agent. Redeploying an application that was set up from the
old file would replace the controller with an agent. Say so in the file, and
add an upgrade path to the README: move the controller to its own service on
the same data volume first, then deploy the agent as a new application.
This commit is contained in:
Alexa
2026-10-25 11:47:49 +02:00
parent 19402459a9
commit 29aca0e88c
2 changed files with 25 additions and 0 deletions
+6
View File
@@ -3,6 +3,12 @@
# /docker-compose.yml and "Connect to predefined network" on. It needs no domain: it dials out to
# Jenkins over WebSocket on Docker's internal network. Set the variables in
# the resource's Environment Variables; see ci/jenkins/README.md.
#
# This file used to define the Jenkins controller itself. If your Jenkins was
# deployed from it, don't redeploy that application from this version: it
# would replace the controller with an agent. Move the controller to its own
# service first and deploy this as a NEW application (README: "Upgrading from
# the old setup").
services:
agent:
build: