You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Automatically start backport builds where possible.
Why is this needed:
🚧 dumped all the input into this ticket, need to clean this issue and make it more concise later 🚧
We have rel-XXX branches where XXX is the major version of a supported Garden Linux version.
This branch currently pulls in changes from a maint-X.Y or main branch where X.Y is the kernel version used, in case main is on something newer already.
Currently the workflow looks like this:
upgrade maint-X.Y branch with latest patch level (semi automated already, but requires manual fixing)
(only for first backport for XXX) create rel-XXX branch and add .container file with correct build container
merge maint-X.Y to rel-XXX
If Maintainer does not merge changes from main-X.Y, we can potentially diverge from the expected source in maint-X.Y, which may lead in missing fixes or patches.
To Remove this source of issue, we propose to add a definition in maint-6.6 to tell the pipelines for what versions the kernel must be build with which container (previously specified in .container).
To allow maintainers to browser git history, and to be consistent with all other packages, the rel- branches must still exist but must be updated by automation.
The text was updated successfully, but these errors were encountered:
What would you like to be added:
Automatically start backport builds where possible.
Why is this needed:
🚧 dumped all the input into this ticket, need to clean this issue and make it more concise later 🚧
We have
rel-XXX
branches where XXX is the major version of a supported Garden Linux version.This branch currently pulls in changes from a
maint-X.Y
ormain
branch whereX.Y
is the kernel version used, in case main is on something newer already.Currently the workflow looks like this:
.container
file with correct build containerIf Maintainer does not merge changes from main-X.Y, we can potentially diverge from the expected source in maint-X.Y, which may lead in missing fixes or patches.
To Remove this source of issue, we propose to add a definition in maint-6.6 to tell the pipelines for what versions the kernel must be build with which container (previously specified in .container).
To allow maintainers to browser git history, and to be consistent with all other packages, the rel- branches must still exist but must be updated by automation.
The text was updated successfully, but these errors were encountered: