You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Let's say I will have Proj1 and Proj2 repos, which use shared files from the Proj-Common repo. So Proj1 and Proj2 will have Proj-Common as a submodule.
Git now supports having submodules follow the tip of a branch instead of a specific commit, using "git submodule add -b work-in-progress https://bitbucket.org/user/proj-common dependencies/proj-common"
So I can have Proj1/2 follow the "tip" of Proj-Common's branch work-in-progress, and when new commits are made in work-in-progress, someone who checked out Proj1 and Proj2 can change the Proj-Common commit they're pointing to by running "git submodule update --remote". However this is a manual task.
Is there a way to configure Pipelines so that when a new commit is made to Proj-Common/work-in-progress branch, it triggers builds of both Proj1 and Proj2 using the latest commit of work-in-progress, to ensure the changes in the dependency haven't broken the builds of the parent projects?