A couple notes about the environment I work in, which your folk may want to take into account.I'm not a C dev, but a system dev. Compiling using containers works fine - someone needs to figure it out and make it work, then you have a consistent environment for developer desktops that is identical to what your final build will be. The developers grab their containers from your internal container repository, so when you update it, they all get the update on the next build. First, you need more than gmake for builds.At least, anyone building everything in gmake is in for a lot of pain and no one will want to take it over. Jenkins is fine for all that high level packaging for Windows, Mac, Unices, AWS, GCP, etc, pushing to internal repos, pushing to external repos like Nuget and Maven's public repos. Jenkins can also handle emails that say exactly what failed, and run Coverity and/or its free competitors on all the branches. We use scripts kicked off by Jenkins to create new branches (feature and release) plus jobs in Jenkins for the new branch to build on every commit, run Coverity at night, and run tests in different environments. We are also Java SAAS shop, where we also do CI/CD using Jenkins. However, I have been using GitLab for building a web site at home, and the tools look like they have strong functionality, very clean, but the CI/CD is more command-line oriented than Jenkins.By that I mean the build is in a wiki-like format that you can edit with VIM, whereas Jenkins stores that config stuff in XML. It should be a fine environment for a C shop.Or for a SAAS shop. All my very best,Rob -- Rob Echlin, B. Eng. 613-266-8311 - Ottawa, Canada - https://linkedin.com/in/robechlin- https://medium.com/@rechlin On Sunday, July 14, 2019, 5:59:17 p.m. EDT, Rick Leir <rleir [ at ] leirtech [ dot ] com> wrote: I have experience with Fedora, Centos and a debian based distro ( Ubuntu!). Fedora is bleeding edge. You will sometimes need to learn something new just to keep the machine usable. And you will be forced to upgrade regularly (is it a yearly thing?). Centos has the same packages, but not bleeding edge and you are not forced to upgrade so often. It is your best choice for a server, but its desktop is not as good as Ubuntu. You said the devs are moving from Windows? I would be cheering, but maybe they do not want to change. The biggest issue might be as you say IDE or devops. Just allow them to install all the tools they want .. VScode, Notepad++, Atom, ... It is hard to predict what they will want installed tomorrow or even ten minutes from now, the choices are very personal. That is fine, installing packages is easy on Centos and Ubuntu. Not always easy on Fedora because of package versions. Ping me directly if you want more on this. You can document it today, and it will be different within days. Cheers Rick On July 14, 2019 5:27:59 PM EDT, "Robert P. J. Day" <rpjday [ at ] crashcourse [ dot ] ca> wrote: On Sun, 14 Jul 2019, J C Nash wrote: Is there a particular reason to specify fedora? the client wants to standardize on a distro that has solid development infrastructure, i recommended fedora, and they were fine with that. most packages will be available across the board, so restricting it to fedora should not cause any major problems. rday To unsubscribe send a blank message to linux+unsubscribe [ at ] linux-ottawa [ dot ] org To get help send a blank message to linux+help [ at ] linux-ottawa [ dot ] org To visit the archives: https://lists.linux-ottawa.org -- Sorry for being brief. Alternate email is rickleir at yahoo dot com