maven - How do I manage inter-branch dependencies in Perforce? -
we using perforce , maven , in situation have 1 branch hosts mature project , branch b, starting dev on uses code hosted in first branch.
i anticipate going forward, there cases check-in branch result in failed compilation in branch b because developers working on them not aware of specific usages , cross-dependencies. , devs waste time updating b code , figure not compiling.
branch/project needs remain own separate entity because it's code used in future project.
can advice me around handling , alleviating such problem? best-practices guys can suggest? appreciated.
you need set build environment:
1) set continuous integration (ci) server, such jenkins. when developer commits branch a, should detect commit , trigger build.
2) when branch completes build, deploys artifacts shared repository. highly recommended (buy not strictly necessary) build branch deploys repository server, such nexus (but repository in source control or ftp server job too).
3) set branch b in ci server, build "trigger" runs whenever build branch succeeds.
4) configure both build configurations email relevant team members (or everybody?) whenever build fails.
also, both branches should depend on repository #2 above. if need entire environment repeatable , self-contained, go repository-in-scm route.
Comments
Post a Comment