In YAML Project (vs. multi-branch) we use SingleSCMSource to allow the user to specify an SCM in the traditional sense, then we wrap it in SingleSCMSource and store that (similar to how we work with multi-branch).

The problem is that we want the YAML Project to share a commit with the inner job it triggers after loading the DSL, and Single SCM Source doesn't produce a transferrable revision state for use with DelegateSCM.

This means that the inner job doesn't necessarily run at the commit which triggered the outer job, and from which it was loaded (if a commit is pushed within a brief window)

One solution to this would be to simply ditch SCM in the YAML Project and use a proper SCM Source, but this has various pros/cons as well.