build-scan-3.png...

build-scan-infrastructure.png...

== Publish a Build Scan

The best way to learn more about what your build is doing behind the scenes, is to publish a link:https://scans.gradle.com[build scan].
To do so, just run Gradle with the `--scan` flag.

[listing.terminal.sample-command]
----
\$ ./gradlew build --scan

BUILD SUCCESSFUL in 0s
${tasksExecuted.raw} actionable tasks: ${tasksExecuted.raw} executed

teamcity-build-scan-plugin.png...

troubleshooting-dependency-management-build-scan.png...

build-scan-trans-dependencies.png...

build-scan-performance-page.png...

link:https://scans.gradle.com[Build scans] will tell you information about the JVM that executed the build when you use the `--scan` option:

[caption= "Build Environment in build scans",link=https://scans.gradle.com/s/sample/cpp-parallel/infrastructure]
image::build-scan-infrastructure.png[Build Environment in Build Scan]

[[sec:configuring_task_using_project_properties]]

gradle-core-test-build-scan-performance.png...

string, "<nil>".

# Scanning

An analogous set of functions scans formatted text to yield
values.  [Scan], [Scanf] and [Scanln] read from [os.Stdin]; [Fscan],
[Fscanf] and [Fscanln] read from a specified [io.Reader]; [Sscan],
[Sscanf] and [Sscanln] read from an argument string.

[Scan], [Fscan], [Sscan] treat newlines in the input as spaces.