Thanks for asking. 1. The runner will get the code automatically. 2. It is mostly used for interpreted code, http://feedback.gitlab.com/forums/176466-general/suggestions/4522830-allow-access-to-build-artifacts-of-gitlab-ci is not contributed yet. 3. No, I would not recommend that. You could make a script where the runner pushes a successful master build to the production server. 4. The other flow is push -> test 5. Depends, continuous delivery != continuous deployment http://puppetlabs.com/blog/continuous-delivery-vs-continuous-deployment-whats-diff
Best regards, Sytse On Tue, Jun 3, 2014 at 3:55 PM, Ryan Sullivan <[email protected]> wrote: > I have been using Git for years but am new to CI. I have a few really > simple newbie questions that I have not been able to find the answers for. > I hope they aren't too unwelcome > > I was wondering what the "normal" workflow is when using something like > GitLab-CI. > > Do people write a script to retrieve the latest compiled code from the > runner server then deploy that to production? > Do people just use the CI server to build and test, then re-build the > project on the production server? > Do people put a runner on the production server its self to handle > production builds? > Is there a "standard" work flow beyond just push -> compile -> test? > Is it, in general, a good or bad idea to have a successful build & test > trigger a production deployment? > > Thanks so much in advance for anyone willing to help out a CI novice. > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/gitlabhq/570cc8ce-818a-433b-b1bb-6caabaad29d3%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/CAEG31mN9k47ouzs1XKNK%3DYpL-FBWL2wpvSubr4VRV%3DhoMNEu_Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
