How To Setup Github Actions For CI/CD

[@NostraDavid2]

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.

[@fs_72]

Great Video as always, thank you Arjan!

[@ArjanCodes]

Thank you, glad you liked the video!

[@mehdicherifi6289]

Thank you. Please 🙏 can you make in the future a video about local runner for windows? Thank you

[@Pharaoization]

Nice, I've literslly just done that!

[@michajas]

Hey! How do you tackle long term statistics for github actions workflows? I'd like to see how my workflows perform over time...

[@AnthonySherritt]

Thanks!

[@ArjanCodes]

Thank you so much!

[@닌닐니니]

Gooood

[@PhilipDenys]

warning intro starts with a dad joke

[@sasidharjanaki5852]

Nice

[@ArjanCodes]

Thank you, glad you liked it!

[@jaimeaznar1181]

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]

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.

[@hasithkashyapa7645]

Too long sometimes too boring