I\'m trying to create a new project configuration for Jenkins build server. To simplify what I\'m trying to do, I will use only two components to describe the problem.
C
1 - would adding project B
as a sub repo of project A
be a possible solution ?
2- (if including the full source code for B should really be avoided) : would pushing builds of B to some B_builds
repo, and adding this repo as a sub-repo of A
be a possible solution ?
Rationale : one way to make the dependency between A
and B
more explicit is to represent it inside the dependencies of the repository.
This would require to add an extra step when managing the A
project :
update `B` sub repo in `A` project, and push this to `A`
each time you produce a new version for B
.
However, you would have a clear view, from A
, about when the versions of B
were integrated (e.g : "we only used B 2.0.1
starting from A 4.3.2
") , and pushing to A
would trigger your usual Jenkins flow.