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

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

Having to push a commit to test the Github equivalent (Actions) was a huge pain. I think I ended up with 80+ commits.

I wish the existing solutions on the Github side worked.

Mildly ironic that you're hosting this on Github.

[ Parent | on HN ]

Re:Show HN: Test your Gitlab CI Pipelines changes locally us... by mdaniel on Wednesday February 24, 2021 @03:52PM (#26255696)

> I wish the existing solutions on the Github side worked.

I did experience a bad outcome using act[0] for a super weird matrix-y workflow, but I'd say for the most part it behaved sanely; did you report your complaints to their issue tracker?

0 = https://github.com/nektos/act

[ Parent | on HN ]

Re:Show HN: Test your Gitlab CI Pipelines changes locally us... by jnwatson on Wednesday February 24, 2021 @04:59PM (#26256630)

I briefly tried it. It couldn’t even parse the yaml.

[ Parent | on HN ]

Re:Show HN: Test your Gitlab CI Pipelines changes locally us... by benibela on Thursday February 25, 2021 @07:37AM (#26262157)

> I think I ended up with 80+ commits.

Happens all the time to me. (although I have not used Actions) . Especially when I also had to set up a cross compiler on the CI. And each change needs 15 minutes to run the VM again

CI is an enormous productivity killer

[ Parent | on HN ]

Re:Show HN: Test your Gitlab CI Pipelines changes locally us... by c7DJTLrn on Thursday February 25, 2021 @07:10PM (#26270054)

Yep, CI like this is a catastrophe. Sourcehut's ad-hoc builds are really nice because you can test without pushing any changes. But sadly, Sourcehut CI is lacking in other areas.

[ Parent | on HN ]