From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Sukhwinder Singh <php_programmer_india@hotmail.com>
Cc: Jacob Keller <jacob.keller@gmail.com>, git@vger.kernel.org
Subject: RE: Git Deployment using existing multiple environments
Date: Tue, 15 Sep 2015 09:48:34 +0200 [thread overview]
Message-ID: <8f9806ed1145d5873aadf6d28d44ad64@dscho.org> (raw)
In-Reply-To: <BAY180-W38D1FC3FD9892A6D147968C25C0@phx.gbl>
Hi,
please stop top-posting. It is quite irritating by now. Thank you.
On 2015-09-15 08:50, Sukhwinder Singh wrote:
> Now lets say we set up a repository at github which has the latest
> code (all test code)., Now at each of our own servers we already have
> existing code, that is Test, UAT and Live. For example, first he'll
> pull code from github to our Test Server and then move branches to UAT
> and then to Live. Can it work?
Yes, it can work.
The major problem here will be that you have only a single, central repository that every developer has write access to, but you expect only a single trusted person to deploy that code via three different stages. That can be tricky, in particular if your trusted person is a newbie.
> If it can work then can I please get some some example commands or the procedure to set it up?
Sorry, this feels a bit too much like "could you please do all my work for me?" to me. And if I really provide exact commands here, I may even be liable when it does not work out in the end? I am not going to do that.
Instead, I will strongly suggest to learn enough about Git to answer those quite simple questions ("How do I pull?", "What is a pull?", "How do I update a test machine's working directory with the newest branch tip?") yourself. I usually recommend https://try.github.io/
> Time is a bit of problem right now or I would have read book suggested by Johannes. I have searched on the internet but couldn't find any similar case.
If I was in your shoes, I would spend the time *now*, rather than quite possibly spending 10x as much time later when I have to clean up a mess. In my experience,
what looks like the cheap route (copying commands without understanding them, really), invariably turns out to be the most expensive route possible.
In any case, this was as much useful feedback as I had to give to your questions.
Ciao,
Johannes
next prev parent reply other threads:[~2015-09-15 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 6:31 Git Deployment using existing multiple environments Sukhwinder Singh
2015-09-12 10:55 ` Johannes Schindelin
2015-09-14 5:55 ` Sukhwinder Singh
2015-09-14 8:32 ` Jacob Keller
2015-09-15 6:50 ` Sukhwinder Singh
2015-09-15 7:48 ` Johannes Schindelin [this message]
2015-09-15 8:12 ` Sukhwinder Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f9806ed1145d5873aadf6d28d44ad64@dscho.org \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
--cc=php_programmer_india@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).