Using Federated Repositories
Learn how Federation affects deployment, resolution, and conflict handling for developers.
This guide explains what Federated repositories mean for developers, build engineers, and other platform users who deploy to, resolve from, and browse artifacts in Federated repositories.
What Developers Need to Know
A Federated repository functions similarly to a local repository from your perspective. You deploy artifacts to it, resolve dependencies from it, and browse it in the Artifacts Browser just like any other local repository. The key difference is that your artifacts are automatically synchronized to identical repositories on other JFrog Platform Deployments (JPDs) across your organization.
How Synchronization Affects Your Workflow
Changes made to artifacts on one Federation member are replicated asynchronously to the other members. This means:
- Deployment: When you deploy an artifact, it is available immediately on your local JPD. It becomes available on remote JPDs after the synchronization completes.
- Resolution: You can resolve artifacts that were deployed on any JPD in the Federation, once synchronization has completed.
- Metadata arrival: A file that is replicated from one Federation member (the source) to a different Federation member (the target) can't be downloaded by users from the target member until it receives the metadata. You can verify the metadata arrival by checking whether the file is displayed in the tree browser.
Note
Starting from version 7.74, SaaS customers can confirm a file's arrival by looking for the following log message:
"Finished the handle mirror event for repo <repo_key> and message: <message>".
CRUD Operations
Any of the CRUD actions (create, read, update, delete) that you perform are automatically applied to the Federation members. You can perform actions according to your permission sets. The logic is applied according to the last action performed on the artifact by any of the users in the Federation.
Conflict Resolution
When the same file is sent from two locations simultaneously, Federation resolves the conflict using timestamp-based conflict resolution: the last event received overrides previous events. This means that if two developers at different sites update the same artifact at the same time, the latest update by timestamp takes precedence.
Related Topics
Updated about 7 hours ago