Skip to content

Conversation

@mbuechse
Copy link
Contributor

From 0 am UTC to 5 am UTC, which is 7 am CEST.

Vastly increases the chance that we catch the latest nightly results from the compliance checks, in particular when they are moved back from 3 am UTC to 0 am UTC, as proposed in a concurrent PR: SovereignCloudStack/zuul-scs-jobs#49

From 0 am UTC to 5 am UTC, which is 7 am CEST.
Vastly increases the chance that we catch the latest nightly results from the compliance checks, in particular when they are moved back from 3 am UTC to 0 am UTC, as proposed in a concurrent PR:
SovereignCloudStack/zuul-scs-jobs#49

Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
@mbuechse mbuechse requested a review from fkr May 26, 2025 12:16
@berendt
Copy link
Contributor

berendt commented May 26, 2025

It's possible to trigger Github Actions by calling an URL. I think it's better to trigger the build of the docs when the compliance check job finished. This way we can ensure a rebuild of the docs after a successful compliance check job.

@berendt
Copy link
Contributor

berendt commented May 26, 2025

@mbuechse
Copy link
Contributor Author

@berendt We should consider this, but this opens quite the can of worms (because what we want to build on demand is only/mainly the results page, and other pages may have other requirements). In the meantime, is there any reason NOT to move the build forward?

@berendt
Copy link
Contributor

berendt commented May 26, 2025

No, I think that's fine with the new schedule. I just wanted to mention this way for the sake of completeness and potential addition in the future.

@mbuechse mbuechse merged commit c786595 into main May 26, 2025
6 checks passed
@mbuechse mbuechse deleted the mbuechse-patch-1 branch May 26, 2025 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants