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 "COSMOS RE AND BUILD WISH LIST"
(→What we need) |
(→Reference) |
||
| (28 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
<!-- CONTENT start --> | <!-- CONTENT start --> | ||
| − | + | = Release Engineering and Build Wish List = | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
<font color="blue"> | <font color="blue"> | ||
<mdw> | <mdw> | ||
| − | + | Since we are opening up enhancement requests, we should tie these back to use cases per our development process. I think many of these, e.g. the download site, would support the idea of the CMDBf toolkit, as an example. | |
| − | + | ||
| − | + | ||
</mdw> | </mdw> | ||
</font> | </font> | ||
| + | = COSMOS needs to have a continuous and well-defined build process = | ||
| + | == Have a functional weekly build == | ||
| + | <ol> | ||
| + | <li><b><font color="green" size="+1">Done</font></b> <b>Process change</b> Until the "fire alarm" email is automated, the build team will manually email cosmos-dev@eclipse.org to notify developers when there is a compile error. Upon seeing a build break email, developers must check the build reports to fix the problem. The Build Reports, which are listed in a link next to the driver link on the download page, provide more details.</li> | ||
| + | <li><b><font color="green" size="+1">Done</font></b> <b>Process change</b> Developers must check in their code more frequently; i.e., at least weekly.</li> | ||
| + | <li><b><font color="green" size="+1">Done</font></b> <b>Process change</b> Developers must use the build rather than relying on CVS alone. Developers must download the build regularly and check out only their plugins rather than relying on HEAD.</li> | ||
| + | <li>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=215135 215135] Establish a process for running JUnits against a COSMOS build</li> | ||
| + | </ol> | ||
| − | < | + | == The download page must have a build that has ALL the components as soon as they become available. == |
| − | + | This should be partly addressed by the actions for <i>Have a functional weekly build</i>. A developer will notice if their component is missing. | |
| − | + | <ol> | |
| − | + | <li>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=216169 216169] Dependencies should be automatically be included in the build package</li> | |
| − | + | </ol> | |
| − | + | == QA Team must be able to start testing before iteration end == | |
| − | + | <ol> | |
| − | <li> | + | <li><b><font color="green" size="+1">Done</font></b> <b>Process change</b> We need to have a weekly integration build. [http://wiki.eclipse.org/COSMOS_BUILD_SCHEDULE Build schedule]</li> |
| − | <li>We need | + | |
</ol> | </ol> | ||
| − | === | + | = COSMOS builds must be run on the eclipse server = |
| − | [ | + | This requirement is key to enable all committers to kick off a build. |
| + | <ol> | ||
| + | <li>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=206374 206374] The infrastructure is set up; we can start running the builds on the eclipse server at any time. We should start this sooner rather than later. The earlier in a release we make build changes the more time that we have to react to the breakages that aren't expected but always occur.</li> | ||
| + | <li><b><font color="green" size="+1">Done</font></b> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=216499 216499] We need to document the build completely so that all committers know how to start a build manually.</li> | ||
| + | <li><b><font color="green" size="+1">Done</font></b> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=216650 216650] We need more disk quota.</li> | ||
| + | </ol> | ||
| − | = | + | = COSMOS needs to be packaged according to adoption scenarios = |
<ol> | <ol> | ||
| − | + | <li>Define the use cases separated by roles (so that we know who needs what). | |
| − | + | <ol> | |
| − | + | <li>Need roles for the Data Collection component.</li> | |
| − | + | <li>Need roles for the Data Visualization component.</li> | |
| − | + | <li>[[COSMOS_Use_Cases#SML_and_SML-IF_validation_support|Read first attempt to define these roles for the Resource Modeling component.]]</li> | |
| − | + | </ol> | |
| − | + | </li> | |
| − | + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=216771 216771] The code must be refactored so that the build can package the code the way that we think that a consumer intends to use it. | |
| − | + | <ol> | |
| − | first attempt to define these roles for the Resource Modeling | + | <li>Need to refactor the code for the Data Collection component as per its roles TBD above.</li> |
| − | + | <li>Need to refactor the code for the Data Visualization component as per its roles TBD above.</li> | |
| − | + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=215357 215357] [http://bugs.eclipse.org/bugs/show_bug.cgi?id=215355 215355] Resource Modeling bugzillas for refactoring | |
| − | + | </li> | |
| − | + | </ol> | |
| − | + | </li> | |
| − | + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=214774 214774] [http://bugs.eclipse.org/bugs/show_bug.cgi?id=209998 209998] Fix other bugzillas for refactoring</li> | |
| − | + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=215610 215610] Involve the build team in helping with feature definition to enable an UpdateManager install and create an update manager site for COSMOS</li> | |
| − | + | </ol> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | = Generate reports and notifications of problems with the build = | |
| − | + | <ol> | |
| − | + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=216591 216591] Build "fire alarm" notification email</li> | |
| − | + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=210263 210263] Fix the copyright reporting tool</li> | |
| − | + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=216630 216630] Detect missing about.html and other files required by legal</li> | |
| − | + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=216654 216654] Detect use of internal API owned by non-COSMOS projects</li> | |
| − | + | <li><b><font color="green" size="+1">Done</font></b> Post list of the defects that are fixed in a build</li> | |
| + | <li><b><font color="green" size="+1">Done</font></b> <b>Process change</b> Developers must specify the bug number in the CVS comments during check-in. This number is used to generate the list of defects that are fixed in a build.</li> | ||
| + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=216655 216655] Generate Javadoc for milestone drivers</li> | ||
| + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=216656 216656] Build Verification Test (BVT), a.k.a. JUnits, results posted next to the build download link</li> | ||
| + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=218050 218050] Investigate running code coverage tool</li> | ||
</ol> | </ol> | ||
| + | |||
| + | = We need agreement on the RE team's responsibilities = | ||
| + | The COSMOS May 2007 F2F had the following discussion [http://wiki.eclipse.org/COSMOS_RE_PROPOSAL RE Responsibilities] | ||
| + | |||
| + | = Reference = | ||
| + | [[COSMOS_RE_AND_BUILD|COSMOS Release Engineering and Build]] | ||
| + | |||
| + | [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=Cosmos&component=cosmos.build&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs opened for the Build component] | ||
| + | |||
| + | [[Build Packaging for COSMOS]] | ||
| + | |||
<!-- CONTENT end --> | <!-- CONTENT end --> | ||
<!-- Category --> | <!-- Category --> | ||
| − | + | [[Category:COSMOS]] | |
Latest revision as of 10:27, 25 March 2009
Contents
- 1 Release Engineering and Build Wish List
- 2 COSMOS needs to have a continuous and well-defined build process
- 3 COSMOS builds must be run on the eclipse server
- 4 COSMOS needs to be packaged according to adoption scenarios
- 5 Generate reports and notifications of problems with the build
- 6 We need agreement on the RE team's responsibilities
- 7 Reference
Release Engineering and Build Wish List
<mdw> Since we are opening up enhancement requests, we should tie these back to use cases per our development process. I think many of these, e.g. the download site, would support the idea of the CMDBf toolkit, as an example. </mdw>
COSMOS needs to have a continuous and well-defined build process
Have a functional weekly build
- Done Process change Until the "fire alarm" email is automated, the build team will manually email cosmos-dev@eclipse.org to notify developers when there is a compile error. Upon seeing a build break email, developers must check the build reports to fix the problem. The Build Reports, which are listed in a link next to the driver link on the download page, provide more details.
- Done Process change Developers must check in their code more frequently; i.e., at least weekly.
- Done Process change Developers must use the build rather than relying on CVS alone. Developers must download the build regularly and check out only their plugins rather than relying on HEAD.
- 215135 Establish a process for running JUnits against a COSMOS build
The download page must have a build that has ALL the components as soon as they become available.
This should be partly addressed by the actions for Have a functional weekly build. A developer will notice if their component is missing.
- 216169 Dependencies should be automatically be included in the build package
QA Team must be able to start testing before iteration end
- Done Process change We need to have a weekly integration build. Build schedule
COSMOS builds must be run on the eclipse server
This requirement is key to enable all committers to kick off a build.
- 206374 The infrastructure is set up; we can start running the builds on the eclipse server at any time. We should start this sooner rather than later. The earlier in a release we make build changes the more time that we have to react to the breakages that aren't expected but always occur.
- Done 216499 We need to document the build completely so that all committers know how to start a build manually.
- Done 216650 We need more disk quota.
COSMOS needs to be packaged according to adoption scenarios
- Define the use cases separated by roles (so that we know who needs what).
- Need roles for the Data Collection component.
- Need roles for the Data Visualization component.
- Read first attempt to define these roles for the Resource Modeling component.
- 216771 The code must be refactored so that the build can package the code the way that we think that a consumer intends to use it.
- 214774 209998 Fix other bugzillas for refactoring
- 215610 Involve the build team in helping with feature definition to enable an UpdateManager install and create an update manager site for COSMOS
Generate reports and notifications of problems with the build
- 216591 Build "fire alarm" notification email
- 210263 Fix the copyright reporting tool
- 216630 Detect missing about.html and other files required by legal
- 216654 Detect use of internal API owned by non-COSMOS projects
- Done Post list of the defects that are fixed in a build
- Done Process change Developers must specify the bug number in the CVS comments during check-in. This number is used to generate the list of defects that are fixed in a build.
- 216655 Generate Javadoc for milestone drivers
- 216656 Build Verification Test (BVT), a.k.a. JUnits, results posted next to the build download link
- 218050 Investigate running code coverage tool
We need agreement on the RE team's responsibilities
The COSMOS May 2007 F2F had the following discussion RE Responsibilities
Reference
COSMOS Release Engineering and Build