Changes between Version 2 and Version 3 of JobPinning


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

--

Legend:

Unmodified
Added
Removed
Modified
  • JobPinning

    v2 v3  
    4343and then run [XaddTool xadd].
    4444
    45 This, 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.
     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. Another issue might be that you are using some other workunit generator than BOINC's create_work tool, and thus the Workunit DB field is not (easily) accessible to you when you create the workunit.
    4646
    4747== Plan Classes ==
     
    6767
    6868Workunits 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>).
     69
     70For a detailed discussion of that feature and its use case see the [https://github.com/BOINC/boinc/pull/2003 github PR].