Change trigger_devel workflow to midday every week day #94

fdegirmenci · 2025-03-17T13:19:10+01:00

fdegirmenci commented

2025-03-17 13:19:10 +01:00

Cron is configured to run every night on a daily basis which is
great. However, this has potential to break all the SV pipelines
as a commit that gets merged to EIB will result in a new image
build without the SV team have chance to validate and reflect the
change to SV.

This commit configures trigger_devel workflow to run midday every
week day so the SV team can make the necessary validations and
updates accordingly.

Please note that this should be considered as a temporary fix and
an automated way to bring new EIB versions to SV should be developed
collaboratively.

Cron is configured to run every night on a daily basis which is great. However, this has potential to break all the SV pipelines as a commit that gets merged to EIB will result in a new image build without the SV team have chance to validate and reflect the change to SV. This commit configures trigger_devel workflow to run midday every week day so the SV team can make the necessary validations and updates accordingly. Please note that this should be considered as a temporary fix and an automated way to bring new EIB versions to SV should be developed collaboratively.

fdegirmenci added 1 commit 2025-03-17 13:19:11 +01:00

Change trigger_devel workflow to midday every week day

Build PR in OBS / Build PR in OBS (pull_request_target) Successful in 37m35s

Details

fb896ffe62

Cron is configured to run every night on a daily basis which is
great. However, this has potential to break all the SV pipelines
as a commit that gets merged to EIB will result in a new image
build without the SV team have chance to validate and reflect the
change to SV.

This commit configures trigger_devel workflow to run midday every
week day so the SV team can make the necessary validations and
updates accordingly.

Please note that this should be considered as a temporary fix and
an automated way to bring new EIB versions to SV should be developed
collaboratively.

fdegirmenci requested review from dprodanov 2025-03-17 13:19:11 +01:00

fdegirmenci requested review from nbelouin 2025-03-17 13:19:11 +01:00

fdegirmenci commented

2025-03-17 13:19:41 +01:00

@nbelouin @dprodanov not sure if i updated the correct workflow but please have a look and let me know what you think.

dprodanov approved these changes 2025-03-18 11:14:02 +01:00

steven.hardy approved these changes 2025-03-20 10:22:20 +01:00

steven.hardy left a comment

This seems OK but perhaps we should instead periodically release a devel image so it's persistent and SV can bump when convenient rather than being forced to potentially do daily updates?

I would imagine doing e.g weekly or sprintly bumps for SV might be enough and involve less work for the team?

This seems OK but perhaps we should instead periodically release a devel image so it's persistent and SV can bump when convenient rather than being forced to potentially do daily updates? I would imagine doing e.g weekly or sprintly bumps for SV might be enough and involve less work for the team?

fdegirmenci commented

2025-03-20 10:27:08 +01:00

This seems OK but perhaps we should instead periodically release a devel image so it's persistent and SV can bump when convenient rather than being forced to potentially do daily updates?

I would imagine doing e.g weekly or sprintly bumps for SV might be enough and involve less work for the team?

Yes, this would make things much easier. What we did this morning is we pushed the latest EIB to GitLab registry and switched SV to use it until we have periodic EIB releases on OBS.

The other thing we discussed is to have a promotion pipeline like

a new EIB gets built on Factory
SV periodically polls OBS for new images and tests them in SV in isolation
the passing images get released on OBS automatically
an MR is opened to SV with the new version which gets reviewed by the team and merged

> This seems OK but perhaps we should instead periodically release a devel image so it's persistent and SV can bump when convenient rather than being forced to potentially do daily updates? > > I would imagine doing e.g weekly or sprintly bumps for SV might be enough and involve less work for the team? Yes, this would make things much easier. What we did this morning is we pushed the latest EIB to GitLab registry and switched SV to use it until we have periodic EIB releases on OBS. The other thing we discussed is to have a promotion pipeline like - a new EIB gets built on Factory - SV periodically polls OBS for new images and tests them in SV in isolation - the passing images get released on OBS automatically - an MR is opened to SV with the new version which gets reviewed by the team and merged

Build PR in OBS / Build PR in OBS (pull_request_target) Successful in 37m35s

Details

This pull request can be merged automatically.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions.

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u trigger-devel-midday-weekdays:fdegirmenci-trigger-devel-midday-weekdays

git checkout fdegirmenci-trigger-devel-midday-weekdays

Sign in to join this conversation.

No Reviewers

nbelouin

dprodanov

steven.hardy

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: suse-edge/Factory#94