git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: Git Deployment using existing multiple environments

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Sep 15, 2015, 07:48 UTC
Message-ID
<8f9806ed1145d5873aadf6d28d44ad64@dscho.org>
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:
Show 5 quoted lines
> 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

Previous: Sukhwinder SinghNext: Sukhwinder Singh
Message 6 of 7 in “Git Deployment using existing multiple environments”
  1. Sukhwinder SinghSep 12, 2015
  2. Johannes SchindelinSep 12, 2015
  3. Sukhwinder SinghSep 14, 2015
  4. Jacob KellerSep 14, 2015
  5. Sukhwinder SinghSep 15, 2015
  6. Johannes SchindelinSep 15, 2015
  7. Sukhwinder SinghSep 15, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.