added Description field for processedDataset and implemented function to remove <inputs> tag from fjr, savannah bug 62916
skipping the import of open blocks of parent dataset from global to local dbs during publication: savannah bug 75848
fixed problem related info consistency, savannah 69184
for multiout
merge 2.7.1_branch
change default: also file with 0 events are published. The option CMSSW.publish_zero_event is deprecated
patch for importParents done by block or file. To be used with DBS_2_0_9_patch6
removed some print
added a warning if publish_with_all_parents = 0 is configured in crab.cfg and dbswriter.insertFiles function called using the parameter insertDetectorData = True, in order to propagate in DBS run and lumisection info. Savannah bug 46566
changes for multiOutput
added a warning if publish_with_all_parents = 0 is configured in crab.cfg
dbswriter.insertFiles function called using the parameter insertDetectorData = True, in order to propagate in DBS run and lumisection info. Savannah bug 46566
Removing deprecated import_all_parents=0 feature
Disable option to use publish_with_import_all_parents so we can reevaluate
added some debug info
added some debug info
import of parent using directly the dbs api
import of parent using directly the dbs api
changed a logger message
sync with head
changed importDataset and importDatasetWithoutParentage calling, using the parameter skipNoSiteError=True to avoid publication stop in the case of block without location
imporoved message. Added a check.
removed '1'
default value for publish_with_import_all_parents is 1, the complete dataset parent tree will be imported in the local DBS
added the key publish_with_import_all_parents, to publish user data in the local dbs importing the complete parents tree
commented patch for importParent
patch for importParentDataset
wrong check
re-add self.pset
other typo
typo
cleanup code for unnecessary try: except: in favour of simpler if
CMSSW.publish_zero_event
some changes to use InspectDBS.py
adapting code to logging usage. (crab_logger removed)
changed importDatasetWithoutParentage with importDataset
changed logger.error in logger.message
added publish_zero_event configurable
removed the check about number of events not 0
added protections and more verbose logs
shorter dataset name in case of production, fixed problem with datasetpath NONE
fix to deal with invalid fjr (skip them instead of let the publication fail)
Take into account only succesfull fjr . See bug #44121
Publication output a bit less verbose (still need to be cleaned)
drop the run/lumisection part compliant with mods in PC FwjobReport
Fix to use the correct processed Dataset in case on datasetpath=None
changes related the new LFN and new datasetpath to publish (task 7471)
- fix the ParentDataset link in DBS - list of fileblocks without duplicate (so that i.e. closing a fileblock is not repeated many times)
added changed for PU_dataset
some changes according to the head of CRAB (24/06/2008)
dataset_pu moved from USER to CMSSW section
added the import of PU dataset in the local DBS
fixed problem with datasetpath none
import parent dataset without all its ancestors
removed ProdAgent API dependencies for DBS publication
Add support for LSF/CAF direct submission Re-establish a correct inheritance pattern for Scheruled* classes Start to remove some unneeded try: catch: statement and replace them with appropriate if:then: Erase any use of cfg_param as a common block (expecially in conjuction with apmon) and replace it with the user of task DB Several minor cleanup
removed a / from the final message
changed user dataset name for data generated by production and added control to writable globalDBS
added some check for data publication
some inprovements for data publication
added a control on dbs_url_for_publication entry
some changes about publication
remove support for DBS1, and remove DBS2 string from files/class
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.