What’s Next for Gitlab CI: Auto DevOps
about.gitlab.com
What’s Next for Gitlab CI: Auto DevOps
1–10 of 91 posts
Re: What’s Next for Gitlab CI: Auto DevOps
#2OP here, just to note - I'm not an employee or affiliated with Gitlab in any way (outside of considering working for them once) -- just a rabid fan.
I've been at companies where I've tried (and failed) to convince other developers/higher ups that something like automatically creating an instance of an app based on the feature branch (what Gitlab/others are calling a "review-app"), is the best way to test individual features with high velocity (of course, this requires one more integration level test in the staging environment to make sure everything works together well). I'm impressed/awed/grateful that Gitlab is pulling these features into their 100% open source solution.
The most common complaints against gitlab are:
- Gitlab's UI is bad-ish (this is what made me consider going to work there/contributing and helping fix that)
- Gitlab is slow
And I think they're dumb. If you think UI on your code hosting tool and slow file operations (on the order of minutes, not hours) to be what would slow their org down, instead of the fact that you haven't automated things that Gitlab wants to automate for free for you (like test deployments actual deployments, build steps), in one coherent place (no juggling github, jenkins, jira, whatever else) then I think you're wrong.
Re: What’s Next for Gitlab CI: Auto DevOps
#3OP here, just to note - I'm not an employee or affiliated with Gitlab in any way (outside of considering working for them once) -- just a rabid fan. I've been at companies where I've tried (and failed) to convince other developers/higher ups that something like automatically creating an instance of an app based on the feature branch (what Gitlab/others are calling a "review-app"), is the best way to test individual f…
The UI is bad period. 85% navigation on a normal laptop display (1080). There are layers and layers of menus and submenus which could easily be combined and make little sense. And i'm not even someone with a 'design aesthetic'.
The 'review-app' pattern is interesting but doesn't scale for more complicated apps. You'd need to create a 'review cluster' for every branch which quickly becomes untenable. It's usually not lack of automation but cost driving down the number of non-prod environments.
I'm actually a big fan of Gitlab but they should probably focus on user experience and Git hosting and let the other sizable number of products/projects which already exist focus on deployment. Spinnaker, for example, is probably what I'd recommend companies adopt for CD if they're looking to go in that direction.
Re: What’s Next for Gitlab CI: Auto DevOps
#4"Gitlab dominates self-hosted git"
Dont you mean, Gitlab,
"2/3 of people surveyed by Bitrise, a CI service you may have never heard of, which is free, are using Gitlab, which is also free"
Re: What’s Next for Gitlab CI: Auto DevOps
#5OP here, just to note - I'm not an employee or affiliated with Gitlab in any way (outside of considering working for them once) -- just a rabid fan. I've been at companies where I've tried (and failed) to convince other developers/higher ups that something like automatically creating an instance of an app based on the feature branch (what Gitlab/others are calling a "review-app"), is the best way to test individual f…
Bad-ish? Try horrible. GitHub has raised the bar too high for Gitlab to spout the tired developer rhetoric that UI/UX doesn't matter.
Re: What’s Next for Gitlab CI: Auto DevOps
#6OP here, just to note - I'm not an employee or affiliated with Gitlab in any way (outside of considering working for them once) -- just a rabid fan. I've been at companies where I've tried (and failed) to convince other developers/higher ups that something like automatically creating an instance of an app based on the feature branch (what Gitlab/others are calling a "review-app"), is the best way to test individual f…
Gitlab's UI is absolutely awful and incredibly slow. Would you say the same for other tools, like email, or your IDE or editor? They literally copied every functionality and UI of GitHub when they started out, and the only difference at the time was that Gitlab was a slower version of Github.
I'm glad you can self-host it, and that they're open source, they've got that going. But if GitHub would ever open source their tool, it's over.
Re: What’s Next for Gitlab CI: Auto DevOps
#7"Gitlab dominates self-hosted git" Dont you mean, Gitlab, "2/3 of people surveyed by Bitrise, a CI service you may have never heard of, which is free, are using Gitlab, which is also free"
The two statements are not mutually exclusive.
Re: What’s Next for Gitlab CI: Auto DevOps
#8I always use http://gitolite.com, thats enough.
nb: I dont see the point of the graph about numbers of questions on SO. A high level of questions = A lot of problem, no :)?
Re: What’s Next for Gitlab CI: Auto DevOps
#9Pretty sure both GitHub Enterprise and BitBucket Server are the dominant self-hosted Git solutions.
Re: What’s Next for Gitlab CI: Auto DevOps
#10OP here, just to note - I'm not an employee or affiliated with Gitlab in any way (outside of considering working for them once) -- just a rabid fan. I've been at companies where I've tried (and failed) to convince other developers/higher ups that something like automatically creating an instance of an app based on the feature branch (what Gitlab/others are calling a "review-app"), is the best way to test individual f…
I work with self-hosted Gitlab daily and I’ve never thought the UI was bad or slow. In fact, I think it works pretty well.
To the other commenters: Do you have any examples?
Also, I’m excited about auto deployment. The less tools one needs to get software shipped, the better.