Make static graph restore the default experience.

[nkolev92]

This is an epic tracking all things relevant to static graph restore and whether there are any blockers/concerns to making it the default.

For readers, you'll need Zenhub to see the linked issues.

Currently this contains all potential issues tagged as static graph.

This doesn't mean they all need to be fixed, just analyzed :)

Note

For customers moving to static graph

• If you want to ensure that your restore is equivalent across static graph and regular restore consider running:

1. Restore with static graph.
2. Restore without static graph

When you run this, at the end of the second restore you should see something like:
All projects are up-to-date for restore.

• Static Graph restore won't warn for invalid projects #9300

[jeffkl]

One potential issue is that static graph evaluation based restore doesn't call any of the older targets like _GenerateRestoreProjectPathItemsPerFramework. People shouldn't be using them as extension points since we prefixed them with _ but there's no enforcement. So if the default switches, these targets won't run any more and people's builds can start failing in very weird ways.

Telemetry would help us greatly here to know how many people are doing this. We might even be able to add a warning in a future release telling people that the targets are going away.

[nkolev92]

That's a great point.
Definitely a smaller concern, but a possibility.

Think advertising the existence of the feature more broadly before making it a default is a good idea.

1ES repos will probably catch a large majority of the scenarios, but you can never have too many dogfooders :)

[jeffkl]

We are spinning up automation to make it the default for all 1ES customers by sending PRs to their repos. I'll update this issue with the problems we have getting people to adopt it.