Hi Marc,
We are not posting artifacts back to source control.
Issue is not with consuming correct version of A, instead B also needs
latest code to compile successfully against A which will break Case 1.
Hope I am not confusing...
Murali
On Monday, July 21, 2014 2:28:25 PM UTC-7, Marc MacIn
Have A produce an artifact indicating the correct revision in whatever SCM
system (git, svn, etc) you are using. Have B consume that artifact, and
sync its local repository to the correct revision prior to building.
On Mon, Jul 21, 2014 at 2:22 PM, Murali Devakumar
wrote:
> Hi all,
>
> We have
Hi all,
We have a Jenkins CI system which builds individual components on checkin
and we have 70+ components and there are compile time dependencies between
components.
Let's take two components; A, B and B consumes A.
Case 1: Code change is A, Jenkins triggers A and on success it triggers