Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Slingshot"
(→Aggregator) |
|||
| Line 1: | Line 1: | ||
| − | + | ||
More discussion in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=297533 Bug 297533]. | More discussion in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=297533 Bug 297533]. | ||
==What is it?== | ==What is it?== | ||
| + | Slingshot is an Über Repository for Eclipse Projects | ||
| + | |||
*An aggregate repository | *An aggregate repository | ||
**Like the simultaneous release repository | **Like the simultaneous release repository | ||
Revision as of 15:24, 14 April 2010
More discussion in Bug 297533.
What is it?
Slingshot is an Über Repository for Eclipse Projects
- An aggregate repository
- Like the simultaneous release repository
- But without the rigours (or quality assurances)
- A means for projects to extend their reach
- Manifests as a p2 and Maven repository
- Target Audience
- Developers/Committers
- Adopters
- Not intended to be included in packages
- Not for end-users
Aggregator
Slingshot is a p2 repository aggregator. It gathers the contributions from multiple project repositories, and combines them into a single repository that is accessible as both a p2 and Maven repository. Only code that has resolvable dependencies is included in the aggregate repository. Unresolved dependencies are reported back to the project.
The aggregator periodically (on the order of nightly or weekly) pulls together the bundles/features from the collection of repositories, ensures that the required dependencies are available, and assembles the aggregation. Only features for which all dependencies can be resolved are included. If a feature's dependencies cannot be resolved, a message is sent to the contact email address informing the receiver of the error.
The aggregated repository connects (via reference) to the most recent version of the release train repository.
The aggregator mirrors the contents of the repositories it aggregates. It retains all code artefacts, including older versions. We need to assess the potential disk space requirements.
Opt in
To participate in Slingshot, a project must provide a " contribution" file (which uses the same format as the release train). This file is typically stored in the project's website CVS. A pointer to this file is provided via the portal using the Project's "slingshotconfigurationurl" attribute (this is a single absolute URL).
Repository
- Links to simultaneous release repository
- Retains all artifacts
- Restricted to milestones and release builds only
- Facilitates reproduceable builds
- Categorizes based on project structure
- Automated
- We don't chase down your dependencies
- That's your job!
Benefits
- Easier for developers to get the project bits
- Avenue for projects to gain exposure
- Not indended for end users
- No quality assurances