tutorial on CI logs

[drammock]

WIP, do not merge

[netlify]

✅ Deploy Preview for learn-scientific-python-org ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	4483d25
🔍 Latest deploy log	https://app.netlify.com/sites/learn-scientific-python-org/deploys/68214333ea7398000839ec9c
😎 Deploy Preview	https://deploy-preview-245--learn-scientific-python-org.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 Accessibility: 97 Best Practices: 100 SEO: 100 PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[henryiii]

Pictures won't be maintainable, they will go out of date quickly (I made that mistake with my azure-pipelines wheel posts; when I rewrote it for GHA pages in the developer guide, I avoided pictures and that was much better. I'd also either just keep in high-level (figuring out how to find logs isn't that hard on most CI services!), or just specialize in one (GHA) and then mention differences at the end.

[drammock]

I forgot I had opened this PR 😅

Pictures won't be maintainable, they will go out of date quickly

I share this concern, which is part of why I didn't finish this yet. However I disagree with the statement that

figuring out how to find logs isn't that hard on most CI services!

I've had numerous contributors say "hey, CIs are failing but I don't know how to find out why". Nowadays for GH Actions or CircleCI it's pretty easy (one click from the PR page, and it auto-scrolls to the failing job step), but Azure Pipelines seems to often trip folks up. After clicking on the failing job in the PR summary, there's a prominent center-screen "N errors / M warnings" link, which then leads to another screen where you have to select all over again which job you want to view. IIRC there's a more direct way to get there (2 clicks instead of 3) but folks often miss it.

[henryiii]

I think that would fit under the "mention differences"; you could say "click on the check to view the logs", then have a callout for the CI services that make it more difficult. (I think Packit-as-a-Service takes the award here for hardest to find logs :) )