DTS nightly build should use dts-configs from develop branch

[DaniilKl]

Component

Dasharo Tools Suite

Device

other

Dasharo version

-

Dasharo Tools Suite version

v2.7.6

Test case ID

-

Brief summary

DTS nightly builds are built every week from develop branch of the meta-dts repository. The purpose of the nightly builds - to allow users to test and use the not released changes in DTS. The changes in DTS that are not yet released can have a dependency on the changes from develop branch of the dts-configs repository, because the develop branch of this repository contains the changes that are not production-ready too. So the nightly builds must use metadata from the dts-configs from the develop branch out of the box.

How reproducible

100%

How to reproduce

1. Boot DTS using nightly.ipxe.
2. Enter shell by pressing s.
3. Execute command source /usr/sbin/dts-environment.sh; echo $DTS_CONFIG_REF.
4. Observe output refs/heads/main.
5. Boot DTS using dts.ipxe.
6. Enter shell by pressing s.
7. Execute command source /usr/sbin/dts-environment.sh; echo $DTS_CONFIG_REF.
8. Observe output refs/heads/main.

Expected behavior

1. Boot DTS using nightly.ipxe.
2. Enter shell by pressing s.
3. Execute command source /usr/sbin/dts-environment.sh; echo $DTS_CONFIG_REF.
4. Observe output refs/heads/develop.
5. Boot DTS using dts.ipxe.
6. Enter shell by pressing s.
7. Execute command source /usr/sbin/dts-environment.sh; echo $DTS_CONFIG_REF.
8. Observe output refs/heads/main.

Actual behavior

Describe above in How to reproduce.

Screenshots

No response

Additional context

Originally reported here: #1041 (comment) :

The problem with nightly builds is that that it still uses main branch of https://github.com/Dasharo/dts-configs by default, while develop branch of meta-dts (nightly) is tested on develop branch of dts-configs.
It can be worked around manually, by entering shell in DTS, exporting DTS_CONFIG_REF variable: export DTS_CONFIG_REF=refs/heads/develop and then running DTS UI again: dts-boot.
But we might want to change this behaviour to be default one for nightly builds, especially if we want to add it to iPXE menu.

Ideas for the implementation:

The first thing that came to my mind was replasing the DTS_CONFIG_REF value via the dts-scripts_git.bb (e.g., by using sed). But I am not sure whether it is the optimal solution.

Do it in Makefile if some variable is set (then set it in EXTRA_OEMAKE in recipe). Or you could maybe just add this export to /etc/profile so it is set by default.

I agree with the propositions. Then we need to trigger it during Yocto build somehow. We can either do it by passing some variable to kas either by export The_VARIABLE ...; kas-container or modifying some kas/*.yml file using, for example, sed in CI. Or we can add a separate YAML file (for example kas-develop.yml) that will be used for building from develop branch.

The key idea here is to make sure the nightly DTS builds use develop branch of the dts-cofnigs out of the box.

Solutions you've tried

No response

[gent33112-wq]

Hi! I'd like to claim this bounty. I have experience with build systems and can work on this. Please let me know the next steps!

[WuXieSec]

I’m looking into this and plan to submit a PR shortly. I’ll focus on making nightly DTS use dts-configs develop branch by default while keeping stable builds on main.

[WuXieSec]

Update: I opened a PR with a minimal fix to make nightly DTS default to dts-configs develop: Dasharo/meta-dts#323

Please take a look and let me know if you prefer passing this via build vars instead of recipe patching.

[gent33112-wq]

Hi! I am interested in claiming this bounty. Please assign it to me. I have experience with similar projects and can deliver quality work. Looking forward to contributing!

[gent33112-wq]

👋 Hi! I'd like to claim this bounty. I'm available to work on this!

[fujijin]

Hi! I’d like to work on this issue.\n\nPlan:\n1) ensure nightly build path defaults to \n2) keep stable release path on \n3) include a simple verification note () in PR\n\nI’ll prepare a patch and PR.

[fujijin]

Hi! I’d like to work on this issue.

Plan:

1. ensure nightly build path defaults DTS_CONFIG_REF to refs/heads/develop
2. keep stable release path on refs/heads/main
3. include a simple verification note (source /usr/sbin/dts-environment.sh; echo $DTS_CONFIG_REF) in PR

I’ll prepare a patch and PR.

[fujijin]

Update: I opened a PR with a nightly-only fix:
Dasharo/meta-dts#325

Approach:

• patch nightly dts-scripts checkout to default DTS_CONFIG_REF to refs/heads/develop
• pin SRCREV to that patched nightly commit
• keep stable flow unchanged

[WuXieSec]

Hi maintainers,

Quick clarification request regarding bounty #1790:

I have implemented and submitted the related changes in:

• dts-scripts: use dts-configs develop by default for nightly builds meta-dts#323
• companion PR (already merged): build: support DTS_CONFIGS_REF override during install dts-scripts#155

Could you please confirm:

1. whether PR Add possibility to populate serials and UUID on Dell OptiPlex/Precision #155 is considered part of the DTS nightly build should use dts-configs from develop branch #1790 bounty scope,
2. and what the final payout condition/assignment is for this bounty?

Thanks!

[DaniilKl]

Could you please confirm:

1. No, the issue Add possibility to populate serials and UUID on Dell OptiPlex/Precision #155 is neither related to nor is a part of the DTS nightly build should use dts-configs from develop branch #1790 bounty.
2. The final payout condition for this bounty is solved issue DTS nightly build should use dts-configs from develop branch #1790 . So far the closest PR that can solve this issue is the dts-scripts: use dts-configs develop by default for nightly builds meta-dts#323 , but it still has some threads left to address.