We are developing several projects that consist of web artifacts using a branching model git-flow.
Refer to: Vincent Driessen git thread branching model
We use the branch developand jenkinsto automatically build and deploy Web artifacts SNAPSHOTto the test environment.
We run manually git flow release startand git flow release finishto create non-snapshot artifacts that deploy in our art and ultimately deploy in prod.
(How to run commands git flow xxx? Here's the cheatsheet )
My question is: how should the workflow for QA work?
Given that:
- We do not want to deploy snapshots in QA
- Well, if the same artifact that we tested in QA is deployed in PROD
- We can make the most of scripts
git flowand a branching model
Looking at the branching model, my best understanding is:
- Create a release branch (e.g.
release/1.1). - Build artifacts from the release branch and check in
QA. - Make changes to the branch
release/1.1and return to step 2 if necessary. - When testing is complete,
finishrelease (merge into master) - Expand the artifact to prod.
Does anyone have experience, especially a step 2? How to uniquely identify artifacts from a release branch?
, maven 1.1.RC1 release-candidate1, 1.1.RC2 , , 1.1 ( ).