3 ms·

I love the Gitlab CI. It’s so easy to create a new project, and the CI is ready to go. No fumbling around, and the integration is great with the Gitlab docker i

I love the Gitlab CI. It’s so easy to create a new project, and the CI is ready to go. No fumbling around, and the integration is great with the Gitlab docker image store.

xtracto 7y ago
I want to second this. I use GitLab for personal projects and have used their CI extensively. My work uses Github and has all the repos hosted there. I tried to start using Github Actions (or whatever it is called?) about a month ago, and just couldn't make sense of it.. does it provision servers from Docker images/docker-compose files? or is it only a "carcass" where I have to add an additional server? can I do everything "as code" or do I have to mingle with the web console ? After spending about 2 hours tinkering I gave up.
- bastardoperator 7y ago
  Really? I was able to throw together an entire CI/CD workflow in Github that builds, tests, measures coverage and deploys to GCE in like 30 minutes. Bringing your own agents looks fairly simple too and follows a GitOps model: https://help.github.com/en/actions/hosting-your-own-runners https://help.github.com/en/actions/hosting-your-own-runners
jazoom 7y ago
It is great, except there STILL is no reasonable way of finding a particular image in the registry. You can't order by date uploaded! Only by name. Which means the order is out of whack as soon as you go from version 9 to version 10. And to make it worse, paging is extremely slow, so it could take an hour of paging into the middle of the list to find the name of the image you're looking for. Even if the image was uploaded 1 minute ago it could be in the middle page. Thankfully I don't have to do this very often, but it's a horrible experience when needed. For similar reasons deleting unneeded images takes forever and is not feasible.
- nerdbaggy 7y ago
  Hmm good point about that. I’ve never really had maybe more than 5 so it hasn’t been an issue. The auto pruning is a pain too.

I love the Gitlab CI. It’s so easy to create a new project, and the CI is ready to go. No fumbling around, and the integration is great with the Gitlab docker image store.

xtracto 7y ago

I want to second this. I use GitLab for personal projects and have used their CI extensively. My work uses Github and has all the repos hosted there. I tried to start using Github Actions (or whatever it is called?) about a month ago, and just couldn't make sense of it.. does it provision servers from Docker images/docker-compose files? or is it only a "carcass" where I have to add an additional server? can I do everything "as code" or do I have to mingle with the web console ? After spending about 2 hours tinkering I gave up.

bastardoperator 7y ago
Really? I was able to throw together an entire CI/CD workflow in Github that builds, tests, measures coverage and deploys to GCE in like 30 minutes. Bringing your own agents looks fairly simple too and follows a GitOps model: https://help.github.com/en/actions/hosting-your-own-runners https://help.github.com/en/actions/hosting-your-own-runners

jazoom 7y ago

It is great, except there STILL is no reasonable way of finding a particular image in the registry. You can't order by date uploaded! Only by name. Which means the order is out of whack as soon as you go from version 9 to version 10. And to make it worse, paging is extremely slow, so it could take an hour of paging into the middle of the list to find the name of the image you're looking for. Even if the image was uploaded 1 minute ago it could be in the middle page. Thankfully I don't have to do this very often, but it's a horrible experience when needed. For similar reasons deleting unneeded images takes forever and is not feasible.

nerdbaggy 7y ago
Hmm good point about that. I’ve never really had maybe more than 5 so it hasn’t been an issue. The auto pruning is a pain too.