BuildMetadata.json stores the git remote url for the repo and that’s good enough to get us to a mp name
We don’t get to spy on the artifacts so it’s not too strong spying I hope. ideally I’d want Azkaban projects to be defined using infra as code principles (like terraform resources). That’s not the current state so I am settling for static links to projects
Why: helps with LinkedIn's internal migration
What changed: added a projectDirectory which helps us identify the subproject in a MP
Tests performed: modified unit tests