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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.