When enabled, this lets Jenkins fully manage the artifacts, exactly like it does when the artifacts
are published to the master.
In this case, the artifacts are stored in the "jobs/[job]/[build-number]/" path in the selected
bucket and prefix path.
This means the following features are enabled:
- artifacts are finger printed and linked to the build
- artifacts can be downloaded directly from the build page in the
S3 Artifact section
- artifacts are automatically deleted when the build is deleted
- the S3 Copy Artifact build step can be used to download artifacts from S3
automatically, helping build complex pipelines