Good CI/CD and SRE Blogs
40 comments
- Quastor (https://www.quastor.org/) - Moreso focused on backend engineering but they have a lot of SRE content too. It's a newsletter that looks at all the big tech engineering blogs and sends out summaries of the interesting posts.
- SRE Weekly (https://sreweekly.com/) - Curation newsletter on interesting links in SRE
- SRE Prodcast (https://sre.google/prodcast/) - Good podcast by Google on SRE. They pick a specific topic and then interview an expert on that so each episode is well focused. They also provide transcripts so you can just read through it instead of listening.
- Resilience in Action (https://podcasts.apple.com/us/podcast/resilience-in-action/i...) - Another good podcast on SRE with interviews.
If you just want a listen of resources, then you should check out the Awesome SRE repo on github - https://github.com/dastergon/awesome-sre
- SRE Weekly (https://sreweekly.com/) - Curation newsletter on interesting links in SRE
- SRE Prodcast (https://sre.google/prodcast/) - Good podcast by Google on SRE. They pick a specific topic and then interview an expert on that so each episode is well focused. They also provide transcripts so you can just read through it instead of listening.
- Resilience in Action (https://podcasts.apple.com/us/podcast/resilience-in-action/i...) - Another good podcast on SRE with interviews.
If you just want a listen of resources, then you should check out the Awesome SRE repo on github - https://github.com/dastergon/awesome-sre
Great list,
I propose 2 young YT channels that worth watching about reliability and observability
- Slight Reliability (https://www.youtube.com/c/SlightReliability) Podcast from Stephen TOWNSHEND
- Is it Observable (https://www.youtube.com/c/IsitObservable) from Henrik REXED
I propose 2 young YT channels that worth watching about reliability and observability
- Slight Reliability (https://www.youtube.com/c/SlightReliability) Podcast from Stephen TOWNSHEND
- Is it Observable (https://www.youtube.com/c/IsitObservable) from Henrik REXED
Good stuff. Thanks. This seems to be along the lines of what I was looking for.
Nice, thanks!
I'm not sure about SRE specific or CI specific writing but at risk of answering another question, here's what comes to mind for me.
In the Operations space my favorite writer is Charity Majors, although a lot of what she talks about isn't OPs specific:
https://charity.wtf/
Rachel by the Bay is also great:
https://rachelbythebay.com/w/
Totally not related, but Phil Eaton's posts on how databases work are super interesting and lack fluff.
https://notes.eatonphil.com/
In terms of CI and builds, I try to write some on this topic for the Earthly Blog. My Bazel article was recently on Hn. Here are my posts:
https://earthly.dev/blog/authors/adam/
Warning though, I also write about lots of other stuff. Are there specific CI topics you'd like to see covered?
In the Operations space my favorite writer is Charity Majors, although a lot of what she talks about isn't OPs specific:
https://charity.wtf/
Rachel by the Bay is also great:
https://rachelbythebay.com/w/
Totally not related, but Phil Eaton's posts on how databases work are super interesting and lack fluff.
https://notes.eatonphil.com/
In terms of CI and builds, I try to write some on this topic for the Earthly Blog. My Bazel article was recently on Hn. Here are my posts:
https://earthly.dev/blog/authors/adam/
Warning though, I also write about lots of other stuff. Are there specific CI topics you'd like to see covered?
> https://earthly.dev/blog/bazel-build/
That is a good read thank you.
That is a good read thank you.
Kind of you to share, Adam! You have awesome podcast episodes as well!
Check this out if you are into podcasts;
https://sre.google/prodcast/
I started a series recently https://sluongng.hashnode.dev/series/bazel-in-ci with focus on setting up Bazel in CI. But I has been trying to write more about CI and the culture around DevX more than Bazel to provide the context for future posts.
You can read DevOpsLinks and The Chief I/O weekly newsletters. You'll find the best blog posts curated from the SRE/DevOps/CloudNative space.
- DevOpsLinks (CI/CD, Cloud Computing, SRE, DevOps): https://faun.dev/newsletter/devopslinks
- The Chief I/O (Distributed Systems, Kubernetes, Cloud Native DevOps): https://faun.dev/newsletter/the-chief-io
Disclaimer: I'm the founder.
- DevOpsLinks (CI/CD, Cloud Computing, SRE, DevOps): https://faun.dev/newsletter/devopslinks
- The Chief I/O (Distributed Systems, Kubernetes, Cloud Native DevOps): https://faun.dev/newsletter/the-chief-io
Disclaimer: I'm the founder.
“Software at Scale” podcast often has great systems related interviews as well:
https://www.softwareatscale.dev/podcast
https://www.softwareatscale.dev/podcast
Thank you!
I write a lot about CI/CD at my job (unsurprising as we are a CI service). While we do have some articles about our platform itself, most of the articles you'll find are more general:
https://semaphoreci.com/category/engineering
We also have a podcast about engineering that frequently touches CI/CD as a topic:
https://semaphoreci.com/podcast
https://semaphoreci.com/category/engineering
We also have a podcast about engineering that frequently touches CI/CD as a topic:
https://semaphoreci.com/podcast
You'll find that most articles touch CI/CD if they are not outright about CI/CD fundamentals.
https://microplatforms.de is a growing collection of DevOps/Platform Engineering/SRE content.
I like the tiny devops guy, lots of practical talk.
https://www.youtube.com/channel/UC5UfX0EgUWlcdQ2RDsq_fcA
https://jhall.io/media/
https://medium.com/wise-engineering/state-of-our-ci-cd-pipel...
Disclaimer: I work for Wise
Disclaimer: I work for Wise
Out of curiosity, I see that opening a PR triggers an automatic branch build, when the code is merge into master is your build process repeated?
If not, which is what the diagram implies, how do you handle two branches with two PRs trying to get merged in, since there is a chance that they will create conflicts with each other. Do you force branch tests sequentially?
If not, which is what the diagram implies, how do you handle two branches with two PRs trying to get merged in, since there is a chance that they will create conflicts with each other. Do you force branch tests sequentially?
We don't allow stale merges so each branch must be fully up to date with master before it can be metged.
This is a bit of a pain in busy repos
This is a bit of a pain in busy repos
Check this repo for SRE https://github.com/upgundecha/howtheysre
For all things SRE and incident management: https://rootly.com/blog
Same.
Even just a maintained “start to finish” of what someone thinks is current best practice for project development would be a fantastic resource.
Even just a maintained “start to finish” of what someone thinks is current best practice for project development would be a fantastic resource.
It seems always to be too specific to an org. to have a general transferable knowledge to share? Kind of.
Some specifics sure. I'm looking more into general trends like when creating a Docker image it's a good idea to X, Y, Z and we use this tool to satisfy X.
Or Docker images have K, L problems that Podman doesn't have. However Podman has W issue so you have to decide which pain you want to live with.
That kind of stuff.
Or Docker images have K, L problems that Podman doesn't have. However Podman has W issue so you have to decide which pain you want to live with.
That kind of stuff.
https://gregoryszorc.com/blog/2021/04/07/modern-ci-is-too-co... is the best article about CI/CD that I’ve ever read. Gregory gets it.
No Martin Fowler please. He doesn't work on real projects now
While it is true that Martin is not a full-time programmer, all his blog posts are reviewed in our software development mailing list. He solicits opinions, introduces amendments based on feedback and has on ocassion even stepped back from publishing an article.
(Source: I am a Thoughtworker since 2006).
(Source: I am a Thoughtworker since 2006).
His blogs are marketing for Thoughtworks......How things are in theory is different from the actual practices....
Customers are intelligent enough to know that they are going to pay for those developers who are _not_ Martin Fowler.
Martin's articles are freely available and are referenced by practitioners around the world.
Martin's articles are freely available and are referenced by practitioners around the world.
Martin Fowler has never worked in ci/CD and SRE, nor has he ever written anything on the subject.
Damn, i stand corrected.
I've never come across any of these articles, even though I quiet often came upon his programming articles.
Sorry for my ignorance.
I've never come across any of these articles, even though I quiet often came upon his programming articles.
Sorry for my ignorance.
It doesn't seems surprising a 2006 article is not up to date with latest ideas.
on a related note, but are there good resources for DevOps/SRE specifically in the public sector (state/county/city/federal gov)?
Good question, would love to also know about some great blogs
The biggest issue (for me when writing about it) is that it's really hard to do this when most keys and values in any source or screenshot are internal to the company. I could go and clean it up with placeholder data, but at that point I'm essentially doing my work twice.
I feel like the space moves fast, and I need a way to keep up with it better. In an ideal world I would want to see best practices for different tools, and pipelines so I can evaluate them and adopt what makes sense.