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 B. B consumes A, while consuming B will NOT sync any latest code just to ensure in case of failure, it's purely because of A. This works fine. Case 2: Code changed in A, B and they are integrated to each other. What I mean is, B needs A changes to compile successfully. We call this as "Cross-Component checkin". Two possible outcome in this case: - A and B will start simultaneous due to code changed and B will fail - A compiles first and then trigger B (case1). Now B will fail, as B does don't latest changes to integrate with A. In both case B fails. How can we avoid B failure without breaking case1 workflow? Any sort of thoughts will be very useful. Thanks, Murali -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
