Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Higgins/Solutions"

m (Nightly Builds)
(Higgins-based Deployment Configurations)
Line 13: Line 13:
 
* [[Nightly Component Builds]] - not a "deployment configuration" in the usual sense; the Higgins project automatically builds some of the [[Components]] every night.
 
* [[Nightly Component Builds]] - not a "deployment configuration" in the usual sense; the Higgins project automatically builds some of the [[Components]] every night.
  
==Higgins-based Deployment Configurations==
+
===Higgins-based Deployment Configurations===
 
This section lists known deployment configurations developed external to the Higgins project, but based on Higgins [[Components]].
 
This section lists known deployment configurations developed external to the Higgins project, but based on Higgins [[Components]].
 
* [[Bandit STS/IdP Deployment]] - Higgins-based STS/IdP service
 
* [[Bandit STS/IdP Deployment]] - Higgins-based STS/IdP service

Revision as of 00:48, 19 September 2007

A Deployment Configuration is a specific combination of Components that, when assembled and deployed, results in an application or service that is identifiable to an end-user as a "whole" app or service.

Nightly Builds

Higgins-based Deployment Configurations

This section lists known deployment configurations developed external to the Higgins project, but based on Higgins Components.

Links

Back to the top