What Did Your Build Agent Pull?
When a build breaks or a package turns out to be bad, the first question is simple: what did our build agent pull? Give each agent its own named token. Then one click shows what it pulled, and one more saves the list.
Give Each Agent Its Own Token
Section titled “Give Each Agent Its Own Token”Make one token for each build agent, and name it after that agent, such as build-agent-1. The
agent’s uploads, downloads and deletes are then recorded under that token, apart from your other
agents and from the people on your team.
Use an organization token for CI. Repository Tokens shows how to make one.
Open the Token’s Activity
Section titled “Open the Token’s Activity”- Sign in to the admin portal as your organization’s owner or an Admin.
- Open Repository Tokens, find the agent’s token, and choose See activity.
The Access Log opens with that token’s uploads, downloads and deletes, newest first. To look at a span of days, set From (UTC) and To (UTC).
See activity sits beside every token on Repository Tokens, and beside each token on a member’s page.
Download the List
Section titled “Download the List”Choose Download CSV to save the rows the page loaded, including the ones Packages only hides. When the token has more rows than the page loaded, choose Download all for this filter to save all of them in one file.
That file stops at 5,000 rows, the newest ones, and the page tells you when it does. To get older rows, narrow the dates and download again.
Each row of the file gives the time, the action, the file, its package and version, the repository, the user or token, the token’s kind and id, the file’s digest, and the token’s name.
What Each Row Records
Section titled “What Each Row Records”Docker pulls and proxy fills record the exact file; other downloads record the package and version.
The File digest column holds the file’s digest where the row records one, and is empty where it does not.
Access Log covers the rest: what the log shows, how far back it goes and what it leaves out.