For the love of your devs, please don't create separate QA and production GitLab instances, it's madness :) You'll use separate Git branches for "production" and "development" code, there quite a few different strategies for this. There's a lot of documentation about Continuous Delivery that explain the workflow for delivering a change from development to production.
HTH, Daniel Serodio On Monday, March 23, 2015 at 5:38:52 PM UTC-3, Wagner Rogério Garcia wrote: > > Guys, good afternoon. > I've never worked with GITLAB, must mount for the company I work a > project with the GITLAB being a QA environment and production. My idea is > to integrate these environment. > My question is this. Need different servers, that is, one for production and > one for QA or have to carry the same GITLAB? I would like to use Jenkins to > integrate. There is another way to do this project? > > Thank U > > Wagner > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/f4b6c6ff-580d-486e-ae10-e89aa227e323%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
