4 ms·
Great idea. One question - what pain point is this solving? As a GitLab, GitLab Pipeline and Docker user I don't find running pipelines that slow to run or ini
by obayesshelton 6y ago
Great idea.
One question - what pain point is this solving?
As a GitLab, GitLab Pipeline and Docker user I don't find running pipelines that slow to run or initiate
- conradludgate 6y agoPersonally with Github Actions, I do find myself pushing 2, 3 or 4 times just getting the pipeline working because I always mess something up, either I've messed up a command or the environment isn't what I expected etc. There's act[0] for github which I should use more often to solve this, but I usually forget [0]: https://github.com/nektos/act https://github.com/nektos/act
- wdb 6y agoYou continuously need to push your changes to change `.gitlab-ci.yml` and find out if your change is working? E.g. your docker run command. I haven't tried out the tool yet but I hope it will save time and avoid me pushing 100s of commits to sort out my pipeline changes.
- carlosf 6y agoThe problem is not necessarily slow init, but some pipelines are just long and complex. If you have a problem in your deployment script, for example, you might need to wait a long time to test and fix it.
- manojlds 6y agoWhy do you say great idea when you didn't even get the pain point it is solving?
- powerapple 6y agoFrom what I understand, you use it as a test for your pipeline scripts. With code we run unittest locally to make sure our commits are okay. When develop ci scripts, many times you only find out things don't work until you push the ci scripts to GitLab, it leaves you with many try and fix commits in history.