Repository navigation
feat: name every image <app>-<os>-<set>-<device> - #35
Merged
Merged
Conversation
tedge-agent-nuttx-esp32s3-devkitc: tiny-edge's esp32s3-devkit NuttX configuration with the module's octal PSRAM as a second heap region, which every feature needs. DEVICES.md records its run on an N16R8 board. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every release image, the firmware name it reports and its firmware entry in Cumulocity now say the operating system: zephyr, idf (ESP-IDF) or nuttx. The variants are zephyr-standalone, zephyr-full, zephyr-ota, idf-full and nuttx-full, and the ESP-IDF agent is named tedge-agent, so the same app's images sit side by side: tedge-agent-zephyr-full-esp32c6-devkitc tedge-agent-idf-full-esp32c6-devkitc tedge-agent-nuttx-full-esp32c6-devkitc The manifest rejects a variant whose name does not match its framework and set, and two builds with the same name. The README's introduction, which still described the first OPC-UA phase, now covers the protocol servers, the device agent and the three operating systems. Devices running an image with an old name update once from the entry with the new name; the README's "Moving a device to the new names" has the table of old and new names. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # README.md # release/devices.yml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Builds on #34 (the S3 NuttX agent). Its base switches to
mainonce #34 merges.Release images only sometimes said which operating system they run. Zephyr images never did (
modbus-server-tedge-full-…), the ESP-IDF image did through its app name (tedge-agent-idf-tedge-onboard-…), and the NuttX image through its variant (tedge-agent-nuttx-…). Now every image is<app>-<os>-<set>-<device>:tedge-agent-zephyr-full-esp32c6-devkitctedge-agent-idf-full-esp32c6-devkitctedge-agent-nuttx-full-esp32c6-devkitc<os>:zephyr,idf(ESP-IDF, with FreeRTOS) ornuttx.<set>:standalone,fullorota, which drops today'stedge-prefix.zephyr-standaloneimages) are exactly 47 characters, the most a device can store.Changes
release/devices.yml:zephyr-standalone,zephyr-full,zephyr-ota,idf-fullandnuttx-full, each with a newsetfield.apps:section namesapps/tedge-agent-idftedge-agent.matrix.py:<os>-<set>for its framework, and two builds with the same firmware name.<app>-<os>-<device>.release/size-baseline.json: re-keyed. The sizes are unchanged.consistent-image-names, which modifies thefirmware-releasespec. It is valid.Devices already in Cumulocity
Each device needs one update from the firmware entry with the new name. The device installs any firmware name, and from then on reports the new one. The old firmware entries stay until someone deletes them.
The next release is 0.17.0. The commit is a plain
feat, because afeat!would make release-please choose 1.0.0.🤖 Generated with Claude Code