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.
Difference between revisions of "OCL/Dev/Releng/Cheatsheet"
< OCL
(New page: == How to Releng MDT OCL == This is a very brief cheat sheet on how to publish builds for MDT OCL. First, there are several types of builds: N-builds: Nightly builds are internal-purpos...) |
(→How to Releng MDT OCL) |
||
| Line 1: | Line 1: | ||
| − | == How to Releng MDT OCL == | + | == How to Releng MDT OCL == |
| − | This is a very brief cheat sheet on how to publish builds for MDT OCL. | + | This is a very brief cheat sheet on how to publish builds for MDT OCL. |
| − | First, there are several types of builds: | + | First, there are several types of builds: |
| + | |||
| + | N-builds: Nightly builds are internal-purpose builds which reflect the current state of the development stream. They do NOT use CVS tags in ocl.map and check out the current HEAD state. These builts are NOT signed and CANNOT be published. | ||
| + | |||
| + | I-builds: Integration builds usually reflect the intermediate state of the product. These are done between milestones and rely on the CVS tags, i.e. their content may differ from the current CVS state. | ||
| − | |||
| − | |||
S-builds: Stable (milestone and release) builds are actually I-builds which have a different naming than I-builds. | S-builds: Stable (milestone and release) builds are actually I-builds which have a different naming than I-builds. | ||
== How to Run an I-build == | == How to Run an I-build == | ||
Revision as of 12:00, 22 March 2010
How to Releng MDT OCL
This is a very brief cheat sheet on how to publish builds for MDT OCL.
First, there are several types of builds:
N-builds: Nightly builds are internal-purpose builds which reflect the current state of the development stream. They do NOT use CVS tags in ocl.map and check out the current HEAD state. These builts are NOT signed and CANNOT be published.
I-builds: Integration builds usually reflect the intermediate state of the product. These are done between milestones and rely on the CVS tags, i.e. their content may differ from the current CVS state.
S-builds: Stable (milestone and release) builds are actually I-builds which have a different naming than I-builds.