What changed, and why it matters
This commit only renames the labels used to pick which GitLab CI runner executes firmware flashing jobs. It does not change any code that runs on the Jade device, nor any build logic, secrets, or network behavior. There is no security relevance visible in the change.
No security action needed. Treat as routine CI infrastructure maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff updates three tags entries in .gitlab-ci.yml flash job templates: esp32flasher → jadedev_flasher, esp32flasher_v1_1 → jade1.1dev_flasher, and esp32s3flasher → jade2.0dev_flasher. These tags are runner selectors only; the surrounding stage, script, variables, and artifacts are unchanged.
Changed components
gitlab/flash.ymlInspect captured patch +3 / −3
diff --git a/gitlab/flash.yml b/gitlab/flash.yml
index 99c380e..a371c0c 100644
--- a/gitlab/flash.yml
+++ b/gitlab/flash.yml
@@ -35,7 +35,7 @@ flash_qemu_psram_unamalgamated:
# Jade v1.0
.flash_jade_template:
stage: flash
- tags: [ esp32flasher ]
+ tags: [ jadedev_flasher ]
script:
- mv $(echo $CI_JOB_NAME | sed "s/^${CI_JOB_STAGE}/build_test/") build
- cp -a build/sdkconfig ./
@@ -77,7 +77,7 @@ flash_jade_ota_delta_ci:
# Jade v1.1
.flash_jade_v1_1_template:
extends: .flash_jade_template
- tags: [ esp32flasher_v1_1 ]
+ tags: [ jade1.1dev_flasher ]
allow_failure: false
flash_jade_v1_1_ci:
@@ -111,7 +111,7 @@ flash_jade_ota_delta_v1_1_ci:
# Jade v2.0
.flash_jade_v2_template:
stage: flash
- tags: [ esp32s3flasher ]
+ tags: [ jade2.0dev_flasher ]
variables:
IDF_TOOLS_PATH: "/home/gitlab-runner/.idf/54"
script:
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.