Skip to content

README: update DTS release process #315

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
DaniilKl wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

README: update DTS release process #315

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 24 additions & 9 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,25 +31,40 @@ This section contains the technical aspects of the `DTS` release process. The
recipients of this information should be those authorised to issue `DTS`
releases.

The basic release process can be found [here][zarhus-release-process]
The basic release process can be found [here][zarhus-release-process].

Follow the first 6 steps from the document linked above. The remaining steps
will be performed automatically by CI. The pipeline of creating a `DTS` release
consists of two steps.
Follow the first 4 steps from the document linked above. After that, open a pull
request from `develop` into `main` in the following repositories:

* The first step is done on GitHub Actions. Here the `DTS` image is built and
* [meta-dts][meta-dts]
* [dts-configs][dts-configs]

The PR in [meta-dts][meta-dts] will trigger a CI/CD with DTS E2E tests. Wait for
the tests to complete, and collect the test results for internal analysis.

After test results analysis and approval from maintainers, do steps 5 and 6 from
[the basic release process][zarhus-release-process]. These steps will trigger
the `DTS` release CI, which consists of two parts:

* The first step is done on GitHub Actions. Here, the `DTS` image is built, and
the binaries are pushed to `boot.dasharo.com`.

* The second step is done on Gitea Actions. There the ipxe menu is pushed to
`boot.3mdeb.com` and the binaries are signed. Additionally, CI publishes the
release on `https://github.com/Dasharo/meta-dts/releases`, from
where binaries can be downloaded.
* The second step is done on GiTea Actions. There, the iPXE menu is pushed to

@iwanicki92 iwanicki92 Feb 11, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* The second step is done on GiTea Actions. There, the iPXE menu is pushed to
* The second step is done on Gitea Actions. There, the iPXE menu is pushed to

Also iPXE script is pushed in GitHub workflow:

meta-dts/.github/workflows/ci.yml

Line 125 in 5da29ac

scp -i ~/.ssh/dts-ci-key dts.ipxe builder@10.1.40.2:boot/dts/

@iwanicki92 iwanicki92 Feb 16, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nvm, didn't notice you mentioned boot.3mdeb.com. It is pushed into both places in both workflows.
Maybe add mention in the previous point that iPXE script is also pushed e.g.:

-Here, the DTS image is built, and the binaries are pushed to boot.dasharo.com
+Here, the DTS image is built, and the binaries and iPXE scripts are pushed to boot.dasharo.com

`boot.3mdeb.com`, and the binaries are signed. Additionally, CI publishes the
release on `https://github.com/Dasharo/meta-dts/releases`, from where binaries
can be downloaded.

When generating the changelog, you can provide your GitHub access token as a
parameter to `generate-changelog.sh`. This will increase the cap on API call
rate, which may otherwise prevent you from running `git cliff`.

After the CIs finish and the DTS release appears in the [meta-dts][meta-dts]
repository release tab, merge the previously opened PR in
[dts-configs][dts-configs].

[zarhus-release-process]: https://docs.zarhus.com/development-process/standard-release-process
[meta-dts]: https://github.com/dasharo/meta-dts
[dts-configs]: https://github.com/dasharo/dts-configs

## Cukinia tests

Expand Down