D
D
donflash2015-04-17 19:01:42
git
donflash, 2015-04-17 19:01:42

What scheme of work with git and deploy would you recommend?

Let's take an abstract project, imagine that it has production / staging branches in the git + separate domains for prod / stag.
There are a bunch of tasks that need to be worked through the project and shown to managers on stag.
The problem is that sometimes you need to show the result of the task #feature1 on the stag, sometimes the result of the task #feature1+#feature2 and so on.
That is, there is a situation when it is necessary to simultaneously show different versions of the application on staging + I am already silent about the partial transfer of the same tasks to prod.
What scheme of work and deployment would you recommend? Thanks

Answer the question

In order to leave comments, you need to log in

2 answer(s)
E
evnuh, 2015-04-17
@evnuh

Well, change the workflow in the git for starters. One feature = one branch. Further, the question will disappear by itself. If you suddenly need to upload a project for testing in a state in which it will never be (for example, two new features without a third, etc.), then make a temporary branch, merge the necessary features into it, upload it for testing, then delete it.
How to deploy branches to the server using git is described here: https://toster.ru/answer?answer_id=519141

D
dmitriy, 2015-04-17
@dmitriylanets

git (gitflow) + codeship

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question