Skip to content

Conversation

ankith26
Copy link
Member

@ankith26 ankith26 commented Jun 7, 2025

To reduce the number of concurrent CI I propose using just one workflow for all "checks" related things where everything can go on sequentially. In this PR

  • coverage and debug python builds are merged into one build to save CI time (and merging them also makes sense)
  • the cppcheck build is now going to execute sequentially after the above build... for no particular reason apart from reducing concurrent CI usage.
  • Any future "checks" builds can be appended to this file in a similar fashion

@ankith26 ankith26 requested a review from a team as a code owner June 7, 2025 13:17
@ankith26 ankith26 force-pushed the ankith26-combine-ci branch from f990414 to d4b6d76 Compare June 7, 2025 13:20
@ankith26
Copy link
Member Author

ankith26 commented Jun 7, 2025

This PR is a precursor to Andrews #3477 and uses some code/ideas from there

oddbookworm added a commit that referenced this pull request Jun 7, 2025
oddbookworm added a commit that referenced this pull request Jun 7, 2025
Copy link
Member

@oddbookworm oddbookworm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks for doing this! 🎉

@Starbuck5 Starbuck5 added the CI Issue with the Continuous Integration (CI), the actions/bots that test things label Jun 8, 2025
@ankith26 ankith26 added this to the 2.5.6 milestone Jun 8, 2025
@ankith26 ankith26 merged commit c14113d into main Jun 8, 2025
14 checks passed
@ankith26 ankith26 deleted the ankith26-combine-ci branch June 8, 2025 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Issue with the Continuous Integration (CI), the actions/bots that test things
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants