[p4] Production environment questions
dank at kegel.com
Tue Apr 9 12:41:20 PDT 2002
steve at vance.com wrote:
> Actually, it's the way I stated it.
> The initial integrate brings the new and potentially
> good/potentially bad files into the local client
> workspace. You will also need to resolve for the files to
> reflect the candidate source state. Note that you haven't
> commited your integrate yet. You're just trying it out.
> Then build and test the candidate state.
> Finish the integration with either a revert if the build
> and test fails or a submit if the build and test succeeds.
It's slowly dawning on me that whoever is doing the integrates
of candidate branches into the stable branch should
do a p4 resolve and do a full test on the ghastly expensive
hardware before committing the changes.
It's also clear that we should merge the stable branch changes
into all candidate branches after each successful update
of the stable branch. That will keep the resolves in the
above step to a minimum.
(And like I said before, now I just have to code up a shell
script that demonstrates all this on a toy project, to
make sure I really can do it all with perforce.)
More information about the perforce-user