Live data from Hacker News

Good CI/CD and SRE Blogs

news.ycombinator.com

31–40 of 41 posts

Re: Good CI/CD and SRE Blogs

#32

https://medium.com/wise-engineering/state-of-our-ci-cd-pipel... 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?

Re: Good CI/CD and SRE Blogs

#33
post #21

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.

Re: Good CI/CD and SRE Blogs

#37
post #23

Earlier quoted context omitted.

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).

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.

Re: Good CI/CD and SRE Blogs

#38

https://medium.com/wise-engineering/state-of-our-ci-cd-pipel... 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?

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

Re: Good CI/CD and SRE Blogs

#40
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.

Post reply on HN