• CodeBlooded@programming.dev
    ·
    edit-2
    1 year ago

    Real talk- I agree with this meme as truth.

    The more and more I use CICD tools, the more I see value in scripting out my deployment with shell scripts and Dockerfiles that can be run anywhere, to include within a CICD tool.

    This way, the CICD tool is merely a launch point for the aforementioned deployment scripts, and its only other responsibility is injecting deployment tokens and credentials into the scripts as necessary.

    Anyone else in the same boat as me?

    I’d be curious to hear about projects where my approach would not work, if anyone is willing to share!

    Edit: In no way does my approach to deployment reduce my appreciation for the efforts required to make a CICD pipeline happen. I’m just saying that in my experience, I don’t find most CICD platforms’ features to be necessary.

    • synae[he/him]@lemmy.sdf.org
      ·
      1 year ago

      You're not advocating against CI like the meme seems to be, but rather for CI builds to be runnable on human's machines and the results should be same/similar as in when running w/in the CI system. Which is what CI folks want anyway.