Show HN: Test your Gitlab CI Pipelines changes locally using Docker

Re:Show HN: Test your Gitlab CI Pipelines changes locally us... by mikewhy on Wednesday February 24, 2021 @10:23AM (#26250811)

Same, my CI has looked like this for years now:

    ./script/prepare-env
    ./script/test
    ./script/build
    ./script/deploy

It's worked in virtually every CI system, and locally. Bonus point, it really points out the amount of ceremony some CI platforms require to map simple commands into their pipelines. Looking at you, CircleCI.

[ Parent | on HN ]

Re:Show HN: Test your Gitlab CI Pipelines changes locally us... by mnahkies on Wednesday February 24, 2021 @12:56PM (#26253179)

I found an approach like this was especially nice on teamcity in conjunction with its template feature.

Individual apps were still able to have whatever specific thing they needed, but you could globally add a step, eg a security scanning tool or slack notification by modifying the template only rather than 100s of build configuration files as the GitHub / circleci approach seems to encourage.

Adding a new pipeline basically just meant naming it and selecting the VCS URL

[ Parent | on HN ]