Changes between Version 9 and Version 10 of Rose/Rose Stem FAQ

Timestamp:

Jul 23, 2020 4:24:33 PM (3 weeks ago)

Author:

Susan Rennie

Comment:

--

Rose/Rose Stem FAQ

@@ -95 +95 @@
 3. Compile and run the stem tests to see which ones fail rose-ana.
 4. At this point you might want to check why the tests are failing. 
- - Most changes that affect the results are listed on the LoseBitComparison page, which is linked on the front wiki page of the relevant code component. From here, you can see which tickets affected which tests.
+ - Most changes that affect the results are listed on the !LoseBitComparison page, which is linked on the front wiki page of the relevant code component. From here, you can see which tickets affected which tests.
  - Alternatively, if you go to <your_branch>/rose-stem/site/meto/<component>/suite-controls.rc you can see which controls have been updated since the last release.
   - You may need to flick back through previous revisions to find all relevant changes
@@ -101 +101 @@
   - Alternatively, if you click on 'blame' at the top of the page, you can see the revision when the control changed. If you click on the revision number (right columm) you will get the change set, which usually includes the ticket number as well.
 5. Once you're satisfied which controls need to be updated, you need to copy the control files to the shared location. For OPS this is "/g/data/access/OPS/KGO/"
- - Create a new directory for the controls, which for example is named "control-t<ticket_number>", either the ticket number which altered the code, or your ticket to update the controls.
+ - Create a new directory for the controls, which for example is named "control-t<ticket_number>", either the ticket number which altered the code, or your ticket to update the controls. If several tickets have contributed to changes, you should instead name the new controls for the revision number of the trunk for which your controls are valid, i.e. "control-r<revision_number>.
  - Into this directory copy the log and work directories, i.e. {{{cp $CYLC_SUITE_DIR/log <your_control_dir>; cp $CYLC_SUITE_DIR/work <your_control_dir>}}}
-6. Modify the <your_branch>/rose-stem/site/nci/<component>/suite-controls.rc to point to your control dir for the relevant tasks.
+6. Modify the <your_branch>/rose-stem/site/nci/<component>/suite-controls.rc to point to your control dir for the relevant tasks. There is a script to do this automatically, which is useful if many controls are being updated. It is held in one of the repositories.
 7. Rerun the stem tests and check that no rose-anas fail.
 8. If necessary, get an ITO to copy the new controls to the correct directory, then repeat the above two steps, with the correct path.