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"

Line 1: Line 1:
 
A '''Deployment Configuration''' is a specific combination of Higgins [[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.
 
A '''Deployment Configuration''' is a specific combination of Higgins [[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.
  
* [[H1a Identity Agent Deployment]] - for Firefox on Windows, Linux, and OSX using a hosted service
+
* [[H1a Identity Agent Deployment]] - for Firefox or IE on Windows, Linux, and OSX using a hosted service
* [[H1b Identity Agent Deployment]] - for IE on Windows using a hosted service
+
 
* [[H2 Identity Agent Deployment]] - for Firefox on Linux and OSX
 
* [[H2 Identity Agent Deployment]] - for Firefox on Linux and OSX
 
* [[H3 Identity Agent Deployment]] - for Firefox on Linux, OSX, and Windows
 
* [[H3 Identity Agent Deployment]] - for Firefox on Linux, OSX, and Windows

Revision as of 09:52, 19 September 2007

A Deployment Configuration is a specific combination of Higgins 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

  • Automated Builds - not a deployment configuration in the usual sense; the Higgins project automatically builds some (and soon all) of the Components every night.

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