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 "OSEE/Deployment"
< OSEE
(New page: ===Deploying A Change=== Depending on the type of action, care must be taken to deploy to an production site. ====Additions modifications of Artifact, Attribute and Relation types==== * ...) |
(→Deploying A Change) |
||
| Line 6: | Line 6: | ||
* If changes to the type model are additions or minor modifications, they can be made directly in the production unified type artifact without down-time. | * If changes to the type model are additions or minor modifications, they can be made directly in the production unified type artifact without down-time. | ||
* If the changes include deletions or renames of types, you will need to coordinate converting the database before making the changes to he types. | * If the changes include deletions or renames of types, you will need to coordinate converting the database before making the changes to he types. | ||
| + | |||
| + | ====Compatible | ||
Revision as of 16:01, 12 February 2013
Deploying A Change
Depending on the type of action, care must be taken to deploy to an production site.
Additions modifications of Artifact, Attribute and Relation types
- If changes to the type model are additions or minor modifications, they can be made directly in the production unified type artifact without down-time.
- If the changes include deletions or renames of types, you will need to coordinate converting the database before making the changes to he types.
====Compatible