Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consolidate our CI runs with a 1-Service-1-OS policy #7765

Closed
wants to merge 22 commits into from

Conversation

pradyunsg
Copy link
Member

@pradyunsg pradyunsg commented Feb 21, 2020

May eventually fix #7279.
Based on a shower thought, described in #7279 (comment).

TODOs:

  • Azure: run all Python versions on Windows
  • Azure: stop running Linux / MacOS checks
  • Azure: run development tooling (linter / docs / vendoring)
  • Travis: bundle development tooling into 1 job
    • we have 5 runners (I think?)
      • tests start sooner, when there's only 5 jobs in the first stage
  • Travis: run release tooling (nox -s prepare-release, nox -s build-release)
  • GitHub Actions: rename + iterate on developer tooling checks
  • GitHub Actions: drop Linux / Windows checks
  • GitHub Actions: add MacOS test checks
  • Document the 1-Service-1-OS policy
    • "development tooling" -> "primary" -> "secondary"
  • Improve documentation to better describe "how stuff works"

@pradyunsg pradyunsg added type: docs Documentation related skip news Does not need a NEWS file entry (eg: trivial changes) C: automation Automated checks, CI etc type: maintenance Related to Development and Maintenance Processes labels Feb 21, 2020
@pradyunsg
Copy link
Member Author

Hmm... We have a cap of 5 concurrent MacOS jobs on GitHub Actions. I think I'll swap things to do:

  • Travis: Linux
  • Azure: MacOS
  • GitHub: Windows

@pradyunsg
Copy link
Member Author

Actually, this PR is getting big and unwieldy -- I'll file multiple smaller PRs.

@pradyunsg pradyunsg closed this Feb 21, 2020
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Mar 22, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Mar 22, 2020
@pradyunsg pradyunsg deleted the consolidate-ci branch April 1, 2020 19:35
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation C: automation Automated checks, CI etc skip news Does not need a NEWS file entry (eg: trivial changes) type: docs Documentation related type: maintenance Related to Development and Maintenance Processes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarify & document our CI strategy
1 participant