🛠️ DevOps Tips 🛠️ If your GitHub workflows or jobs are failing due to jobs concurrently accessing and/or modifying shared resources, You can control execution at the workflow or job levels using the concurrency.
Jobs/Workflows in the same are prohibited from running at the same time, and you can cancel any jobs/workflow if you trigger another one.
Groups let you define compartments in which you don't want concurrent workflows running. They can be organized however you like. I find that using them in separate environments is a great practice.
Cancel-in-progress: specifies if the old running job/workflow needs to shut down.
Read more in docs: https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency
I built my most recent pitch deck with Claude Design and I'm loving it
0
44
I made a sci-fi trailer about a world where humans forgot how to be human. The scariest part? It is not that far from now. #RunwayBigPitchContest (https://www.linkedin.com/search/results/all/?keywords=%23runwaybigpitchcontest&origin=HASH_TAG_FROM_FEED)👇
I build solid back-end utilities and automation tools, etc.
New to Contra
I build solid back-end utilities and automation tools, etc.
I will engineer high performance Rust software and systems 😊
0
33
I build Rust backend tools for one specific task. You get a compiled application that's small and keeps core logic separate from how it delivers results. This is great, for private servers and automated pipelines. I do not use architecture. I provide solutions only.
1
75
Engineering Principles
1
1
61
asteri* Systems Language Design (Work in Progress)