The basics


You can add new content to the Cloudsmith map by using Cloudsmith's mapping wizard to map your own repository. Once you have added components to the map, you can use them to create new virtual distros.	You can create new mapping jobs using the Mapping Wizard, or manage and monitor existing mappings, through the Repo Mapping section of the Cloudsmith site.

Repository


Cloudsmith currently maps SVN, CVS or Maven repos, Eclipse update sites and ordinary download sites. The repo must be accessible over the Internet, either directly or through a user/password login.	You can map either the entire repository, or just specified components within it. You can choose to have the repo re-mapped at regular intervals, or manually, and you can set times to launch jobs. Mapped content is visible in the publishing space you selected in the Mapping Wizard.

How it works

Newly created mapping jobs are placed in an execution queue and processed in the order received. (Latency will vary with server load.) When the request is executed, a mapper explores the repository, retrieves available metadata regarding to components found and then maps their dependency structure. This information is then added to the global map maintained at Cloudsmith.

If a private publishing space target was selected in the wizard, mapped content will be available only to users with access to that space. Content mapped to a public space will be visible to all users.

You can monitor and control the status of active mapping jobs, and review a log of errors and exceptions, in the repo mapping section of the site. You can also edit settings and properties for scheduled jobs.

You can stop the execution of an active mapping job. If the job is scheduled for execution but not yet executing, stopping it will unschedule it. If it is already executing, execution will stop as soon as possible. (Note that partially mapped content may be visible in the target publishing space.)