How To Setup Github Actions For CI/CD

  Рет қаралды 33,239

ArjanCodes

ArjanCodes

Күн бұрын

Пікірлер: 15
@NostraDavid2
@NostraDavid2 2 жыл бұрын
I did my thesis on CI/CD. The two books (Continuous Integration by Paul Duvall, and Continuous Delivery by Jez Humble) were a great help to deeply understand what's what. The CI book is somewhat outdated and is only interesting for historical purposes. The CD book still holds up (though we have Jenkins instead of Hudson, nowadays). It won't teach you any specific tool, unless you get cracking and actually try to install one, but the deeper understanding helped.
@AnthonySherritt
@AnthonySherritt 2 жыл бұрын
Thanks!
@ArjanCodes
@ArjanCodes 2 жыл бұрын
Thank you so much!
@fs_72
@fs_72 2 жыл бұрын
Great Video as always, thank you Arjan!
@ArjanCodes
@ArjanCodes 2 жыл бұрын
Thank you, glad you liked the video!
@mehdicherifi6289
@mehdicherifi6289 2 жыл бұрын
Thank you. Please 🙏 can you make in the future a video about local runner for windows? Thank you
@michajas
@michajas Жыл бұрын
Hey! How do you tackle long term statistics for github actions workflows? I'd like to see how my workflows perform over time...
@Pharaoization
@Pharaoization 2 жыл бұрын
Nice, I've literslly just done that!
@jaimeaznar1181
@jaimeaznar1181 2 жыл бұрын
How can you make it so that the python and requirements installation only run when there are changes to it and not everytime you want to test? …would you create a workflow with just the testing part?
@marcotroster8247
@marcotroster8247 2 жыл бұрын
It's actually crucial to reinstall everything on each workflow run because the pipeline will give you the confidence that the installation procedure still works. You don't want to end up with a cached pipeline that stopped working several months ago without you noticing. And now that your build server went down, you have to run the procedure on another server where the procedure doesn't work which means you're out of business, cannot ship any hot-fixes for severe bugs or security holes, etc. You want to automate every step from launching a fresh build machine, installing the compiler, downloading the source code, compiling / linting / testing up to finally dropping a releasable product. CI/CD is about keeping the whole procedure up-to-date such that you don't depend on specific machines or hardware. And a practical tip: You don't need to care about the hardware too much. GitHub workflows grants several thousand free hours of compute per month to every publicly available repository. You'll hardly ever exceed that limit with any small to mid size project. So, it's not your hardware that will suffer from reinstalling stuff all the time.
@닌닐니니
@닌닐니니 2 жыл бұрын
Gooood
@PhilipDenys
@PhilipDenys Жыл бұрын
warning intro starts with a dad joke
@sasidharjanaki5852
@sasidharjanaki5852 2 жыл бұрын
Nice
@ArjanCodes
@ArjanCodes 2 жыл бұрын
Thank you, glad you liked it!
@hasithkashyapa7645
@hasithkashyapa7645 2 жыл бұрын
Too long sometimes too boring
4 Tips for Building a Production-Ready FastAPI Backend
27:02
ArjanCodes
Рет қаралды 75 М.
GitHub Actions Tutorial - Basic Concepts and CI/CD Pipeline with Docker
32:31
TechWorld with Nana
Рет қаралды 1,6 МЛН
“Don’t stop the chances.”
00:44
ISSEI / いっせい
Рет қаралды 62 МЛН
So Cute 🥰 who is better?
00:15
dednahype
Рет қаралды 19 МЛН
黑天使被操控了#short #angel #clown
00:40
Super Beauty team
Рет қаралды 61 МЛН
Пишем реальный CI/CD пайплайн | GITLAB CI/CD на практике
19:10
Continuous Integration with GitHub Actions and Python - Part 1: Linting
16:35
Programming with Alex
Рет қаралды 2,6 М.
GitLab CI/CD Pipeline Tutorial for Beginners (2024)
19:33
Valentin Despa
Рет қаралды 62 М.
GitHub Actions CI/CD pipeline | Step by Step guide
46:24
Bouali Ali
Рет қаралды 29 М.
GitHub Actions (Branch Protection, Automated Testing) - Full Tutorial
29:56
How to design a modern CI/CD Pipeline
9:59
DevOps Journey
Рет қаралды 182 М.
“Don’t stop the chances.”
00:44
ISSEI / いっせい
Рет қаралды 62 МЛН