Only using docker to deploy to production is a narrowminded view of CD. There are lots of ways to deploy, like running installers on a remote machine, publishing to IIS, etc. Not everything runs on docker. Not everything runs on Linux (unfortunately). Just take a look at octopus ie. That's CD, almost done right. Non web development (still the major part of dev) is being left out here (again). Anything can be in git, so you should be able to deploy anything as well! I'm left with the feeling: nice if you do web on docker, but we can't use it in our setup. Still prefer octopus in our case to do CD. It all feels like the same narrowminded view on issue management in gitlab where jira rules and gitlab is not even coming close. This just doesn't work, not even in smaller companies, who might do development in non web projects. This works only if you're building websites and you are able to run it in docker. Where is gitflow support for instance in gitlab? Where are issue workflows? Where is scrum and kanban support, story points? That's what companies need today, before even thinking about CD. I think these are the things gitlab should focus on instead doing CD, halfbaked. That's why we use jenkins, jira and confluence. because gitlab doesn't offer us a usable solution for those. And we're not even a big company. Gitlab could be so much more, but it seems to be focussing on the wrong things (like an integrated IDE). Do what you have better instead adding new stuff that hardly anybody uses. Just my 2 cents...
Only using docker to deploy to production is a narrowminded view of CD. There are lots of ways to deploy, like running installers on a remote machine, publishing to IIS, etc. Not everything runs on docker. Not everything runs on Linux (unfortunately). Just take a look at octopus ie. That's CD, almost done right. Non web development (still the major part of dev) is being left out here (again). Anything can be in git, so you should be able to deploy anything as well! I'm left with the feeling: nice if you do web on docker, but we can't use it in our setup. Still prefer octopus in our case to do CD.
It all feels like the same narrowminded view on issue management in gitlab where jira rules and gitlab is not even coming close. This just doesn't work, not even in smaller companies, who might do development in non web projects. This works only if you're building websites and you are able to run it in docker.
Where is gitflow support for instance in gitlab? Where are issue workflows? Where is scrum and kanban support, story points? That's what companies need today, before even thinking about CD. I think these are the things gitlab should focus on instead doing CD, halfbaked. That's why we use jenkins, jira and confluence. because gitlab doesn't offer us a usable solution for those. And we're not even a big company. Gitlab could be so much more, but it seems to be focussing on the wrong things (like an integrated IDE). Do what you have better instead adding new stuff that hardly anybody uses. Just my 2 cents...