[manjari25]

Why?

The Tango analyzer, its fake server and its schema are in place, but nothing in the local demo uses them. This adds an option to run the demo with it, so conflicts between batches can be seen following a build-target graph instead of directory overlap.

What?

• make local-submitqueue-start PROVIDER=git ANALYZER=tango swaps demo-queue's analyzer for Tango and runs the fake Tango server beside the stack. Stop with the same variables. Only PROVIDER=git supports it, because the fake reads targets from that provider's repository.
• The sandbox gets a TARGET file per demo/NN folder, committed on top of whatever is there. demo/00 and demo/01 are libraries, and even folders depend on demo/00 and odd folders on demo/01. Changes in different folders can now conflict.
• make demo-requests refuses a FOLDERS above 10 against a sandbox seeded this way, since only demo/00 to demo/09 have targets and changes elsewhere would never conflict.
• QUICKSTART.md and the provider README describe the option

Test Plan

• make local-submitqueue-start PROVIDER=git ANALYZER=tango, then make demo-requests PROVIDER=git COUNT=8 FOLDERS=10.
• The target_signature table in the application database has a row per batch.
• batch_dependent links changes in different folders that depend on the same library.
• FOLDERS=12 fails right away with an error.
• make local-submitqueue-stop PROVIDER=git ANALYZER=tango removes the stack, including the fake server.
• Unit tests
• CI

Issue