[CI][docs] Put all the doxygen workflow triggers into one file.#22694
Open
hageboeck wants to merge 1 commit into
Open
[CI][docs] Put all the doxygen workflow triggers into one file.#22694hageboeck wants to merge 1 commit into
hageboeck wants to merge 1 commit into
Conversation
hageboeck
added
skip ci
Test Results0 tests 0 ✅ 0s ⏱️ Results for commit 51e3960. ♻️ This comment has been updated with latest results. |
Instead of having one workflow file for every job, the jobs can be moved into one file. They trigger at 1:20 h, because github docs claim that triggering at the full hour creates big load spikes.
hageboeck
force-pushed
the
doxygen_oneTrigger
branch
from
3724c84 to
51e3960
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Instead of having one workflow file for every job, the jobs can be moved into one file. They trigger at 1:20 h, because github docs claim that triggering at the full hour creates big load spikes.
There is already a second trigger at noon to trigger master, but I would first like to see the schedule working before moving master into the same file.