Activity
The Activity page of a repository records what happened to it: which files arrived, their origin, and what changed in the settings.
What the page shows
The list is in reverse chronological order, and related events are grouped into one entry: a deploy of one version is one entry regardless of how many files it contains, and so are the files fetched from one upstream for one build. An entry shows how many files it contains, who caused it, and when. Expand it to see each file, and open a file to see its activity history and origin. A settings change is a separate entry.
The chips at the top narrow the list to deploys, fetches from upstreams, deletions, the index, or settings changes, and to one person or token.
Anyone with the Read repository role sees the file events. Settings changes are shown only to people with the Admin role, and the Settings chip appears only for them.
| Event | What it means |
|---|---|
| Deploy | A file was deployed to the repository |
| Replace | A deployed file replaced an existing file |
| Cache | A file was fetched from an upstream and stored |
| Delete | A file was deleted |
| Index publish | The Maven index got a new incremental part |
| Index reset | The Maven index was rebuilt from the start |
Each event names the path and who caused it: the account or the token that deployed the file, or the upstream that it was fetched from and the account or token whose request caused the fetch. A replacement also shows the file that it replaced.
The file page shows the events for one path.
Settings changes
| Event | What it means |
|---|---|
| Repository created, updated, or deleted | The repository or one of its settings changed |
| Upstream added, updated, removed, or reordered | An upstream changed |
| Content rule added or removed | A content rule changed |
| Access granted or revoked | An account or token was granted or lost access |
| Domain added, removed, or status changed | A custom domain changed |
| Primary domain changed | Another custom domain was made primary |