feat: add artifact upload token credential

README.md

@@ -71,6 +71,12 @@ Jenkins itself.
    `secrets/jenkins_admin_password.txt`. Note the printed password - you'll
    need it to log in. Nothing in `secrets/` is committed to git.
 
+   The Ultra V2 pipeline also needs the artifact server token in
+   `secrets/artifact_upload_token.txt`. Copy the value of
+   `ARTIFACT_UPLOAD_TOKEN` from the artifact server's `.env` file into that
+   file. Docker exposes it only to the controller, and JCasC registers it as
+   the masked Secret Text credential `mate-updates-upload-token`.
+
 3. **Build and start everything**:
 
    ```bash

controller/casc/jenkins.yaml

@@ -68,6 +68,12 @@ credentials:
                 directEntry:
                   privateKey: "${GITEA_ULTRA2_APP_PRIVATE_KEY}"
 
+          - string:
+              scope: GLOBAL
+              id: "mate-updates-upload-token"
+              description: "HTTPS upload token for updates.sparksoftdesign.com"
+              secret: "${ARTIFACT_UPLOAD_TOKEN}"
+
 unclassified:
   location:
     url: "https://jenkins.sparksoftdesign.com/"

docker-compose.yml

@@ -14,6 +14,8 @@ services:
         target: GITEA_ULTRA2_APP_PRIVATE_KEY
       - source: jenkins_admin_password
         target: JENKINS_ADMIN_PASSWORD
+      - source: artifact_upload_token
+        target: ARTIFACT_UPLOAD_TOKEN
     volumes:
       - jenkins_home:/var/jenkins_home
       - ./controller/casc:/var/jenkins_home/casc_configs:ro
@@ -54,3 +56,5 @@ secrets:
     file: ./secrets/gitea_ultra2_app_key
   jenkins_admin_password:
     file: ./secrets/jenkins_admin_password.txt
+  artifact_upload_token:
+    file: ./secrets/artifact_upload_token.txt