Ask HN: How can we make the current CI/CD ecosystem better?

Re:Ask HN: How can we make the current CI/CD ecosystem better? by rpep on Monday December 12, 2022 @02:29AM (#33951934)

I’m not sure the niggles here are platform things - they’re hard lessons that come from experience in using CI for the most part.

Generally you want to aim for writing things in scripts that your CI system calls, so that they can be run locally trivially and so that migrating away from one CI provider (for whatever reason - cost, employer decides to shift, etc.) is not a huge piece of work.

[ Parent | on HN ]

Re:Ask HN: How can we make the current CI/CD ecosystem better? by chillfox on Monday December 12, 2022 @03:02AM (#33952128)

So if we have to use a script anyway, then why do we have to write like 20+ lines of YAML to run the script?

Edit: I mean, why is this not the config if we are just doing a script?

  src: github.com/...
  run: test_and_build.sh

[ Parent | on HN ]

Re:Ask HN: How can we make the current CI/CD ecosystem better? by rpep on Monday December 12, 2022 @05:50AM (#33953271)

It's not that bad:

  jobs:
    unit-tests:
      runs-on: python:3.8.15-slim-buster
      - name: "Run tests"
          working-directory: ./bin
          run: unit-tests.sh

[ Parent | on HN ]