The skipDefaultCheckout() directive is currently only supported within the options for the whole pipeline.

We would like to see this option supported as a property of an agent, to allow default checkout to be skipped on specific stages.

In our scenario we cannot apply this to the whole pipeline and explicitly checkout in the relevant stages, as source files are queried to set environment variables for the pipeline - which (AFAIK) occurs before the start of the first stage.

We have a requirement to perform additional actions, post normal build, on other architectures (through remote agents).  These do not require the source code, as anything can be provided through stash/unstash or equivalent mechanisms. Some of these agents do not have access to the SCM used for the project.

Allowing the skipDefaultCheckout() to be applied to an agent would solve our issues in this regard.