Motivation
The Papertrail service has recently become generally available for all teams to use as part of their normal publishing workflow. Papertrail was created to support the Authorized Publication SSDLC policy requirement. If you use Papertrail to trace all release artifacts, you are fully compliant with this policy.

You may close this ticket as Won’t Do if you don’t plan to use the Papertrail service, which means you will be expected to comply with go/ssdlc-policy by populating the documentation manually. 

What is Papertrail?

TLDR: Papertrail is a service that allows product teams to track various bits of release metadata per artifact that they publish, operated by the DevProd Release Infrastructure team. For details, we recommend reading our Papertrail documentation

How do I use Papertrail?
If your product uses Evergreen to trigger product releases:

• Use the new papertrail.trace command to interact with this service. You may use this reference commit to the Java driver as an example of how to use this command in your project.
• Since Papertrail is an authenticated service, when you’re ready to use this service, request credentials by go/create-issue for DEVPROD with “Release Infrastructure” Service selected titled “Papertrail Service Credentials needed”.

If your product does not use Evergreen to trigger product releases:

• You will not be able to communicate with Papertrail by default due to network security requirements. Please reach out by filing a DEVPROD ticket for “Release Infrastructure” service, so that we can work on possible solutions with you (which may include procuring a static IP address for your builds or running a separate task in Evergreen).

We welcome all questions about this service or general release questions in #ask-devprod-release-tools.