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

Re: Git Architecture Question

From
Manuel Doninger <manuel.doninger@googlemail.com>
Date
Dec 28, 2010, 17:23 UTC
Message-ID
<AANLkTi=Rah9tTUE-vrAqosxqQbPhW8RpOgfEsB_dZJut@mail.gmail.com>
In-Reply-To
<20FFFEFA-5808-4673-B876-C5F76B52D12E@gmail.com>

Hi Anuj, i'm facing a similar problem at the moment. In my company we want to switch from CVS to Git and Ant to Maven/Hudson. We have a similar environment like you, Development, Testing and Production, and my plan at the moment is to have a development, testing and master branch. Every of these branches should represent the appropriate environment. Then I configure Hudson with 3 jobs, every job to build one of these branches and to deploy to a separete folder on our server. If the developers then create a new change in a feature branch, we would merge that feature branch into branch development for our internal tests, then later merge that into testing for our QA department if they say they want to test that change, and if they say it's ok, merge that change into master to deploy it in production environment. This workflow is though not in production use, we evaluate this and other workflows at the moment, so I don't have any experiences from daily work.

Cheers, Manuel

Previous: Anuj GakharNext: Maaartin
Message 2 of 3 in “Git Architecture Question”
  1. Anuj GakharDec 28, 2010
  2. Manuel DoningerDec 28, 2010
  3. MaaartinDec 29, 2010

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.