Changes between Version 1 and Version 2 of JobPinning


Ignore:
Timestamp:
Jul 26, 2018, 3:30:42 AM (3 years ago)
Author:
bema
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • JobPinning

    v1 v2  
    4242}}}
    4343and then run [XaddTool xadd].
     44
     45This, however, requires you to specify exactly one app version that is to be used for a given workunit at the time when the work is generated. This migth not work in all cases, e.g. if you issue a new app version (possibly for a few platforms only) that is compatible to the previous one, but not to the pre-previous one, and you have still workunits for the oldest app version in the DB.
     46
     47== Plan Classes ==
     48
     49So here's a fourth way using plan classes:
     50To the plan classes of the old app versiomn add
     51{{{
     52    <plan_class>
     53        <name>apppc</name>
     54        ...
     55        <max_wu_id>12345</max_wu_id>
     56    </plan_class>
     57}}}
     58
     59Add a new plan class for the new app version(s)
     60{{{
     61    <plan_class>
     62        <name>apppcNEW</name>
     63        ...
     64        <min_wu_id>12346</min_wu_id>
     65    </plan_class>
     66}}}
     67
     68Workunits up to ID 12345 will be processed with app versions using the old plan class "apppc", workunits from ID 12346 on will be processed with app versions using the new plan class "apppcNEW". There exist similar tags to restrict plan classes to batches (<min_batch> and <max_batch>).