#!/usr/bin/python """ This program should lock a perforce label. The only command line parameter is the label p4lock.py LABEL """ import isitalabel import os import re import sys def lock (label): x = isitalabel.check(label) if x == 0: print("There is no label %s.") % (label) sys.exit(1) label_pattern = re.compile(r"^Label:\s+.*") lock_pattern = re.compile(r"^Options:\s+unlocked") tempfile = open("temp.txt", "w") linelist = [] # owner.txt is a one line file generated by the p4unlock.py script. It saves # the name of the label owner so it can be put back by this script. # The owner line is removed by p4unlock.py because Perforce doesn't allow # anyone except the owner of a label to update the label. found_owner = True if os.path.isfile("owner.txt"): ownerfile = open("owner.txt", "r") for line in ownerfile.readlines(): owner = line ownerfile.close() os.remove("owner.txt") else: found_owner = False for line in os.popen("p4 label -o %s" % (label), "r").readlines(): if found_owner: match = label_pattern.match(line) if match != None: linelist = linelist + ["Owner:\t%s\n" % (owner)] line = lock_pattern.sub(r"Options: locked", line) linelist = linelist + [line] tempfile.writelines(linelist) tempfile.close () os.system("p4 label -i < temp.txt") os.remove("temp.txt") def main(): if len(sys.argv) < 2: print ('Invalid input') print ('You must specify a label') print ('usage: p4lock.py LABELNAME') else: label = sys.argv[1] lock(label) ########################################################################### # main if __name__ == '__main__': main()
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#3 | 26652 | Robert Cowham |
This is Tom's change: Introduced new 'Unsupported' directory to clarify that some files in the SDP are not officially supported. These files are samples for illustration, to provide examples, or are deprecated but not yet ready for removal from the package. The Maintenance and many SDP triggers have been moved under here, along with other SDP scripts and triggers. Added comments to p4_vars indicating that it should not be edited directly. Added reference to an optional site_global_vars file that, if it exists, will be sourced to provide global user settings without needing to edit p4_vars. As an exception to the refactoring, the totalusers.py Maintenance script will be moved to indicate that it is supported. Removed settings to support long-sunset P4Web from supported structure. Structure under new .../Unsupported folder is: Samples/bin Sample scripts. Samples/triggers Sample trigger scripts. Samples/triggers/tests Sample trigger script tests. Samples/broker Sample broker filter scripts. Deprecated/triggers Deprecated triggers. To Do in a subsequent change: Make corresponding doc changes. |
||
#2 | 26060 | C. Thomas Tyler |
This supercedes review-24715. Bringing over recent bug fixes and code clean up from Rusty Jackson's local branch. Adds an edge maintenance script to unload clients on edge servers. Automated setting up maintenance.cfg from mkdirs.cfg settings. Cleaned up sdputils.py - It had a logic bug, and fixed all scripts based on changes. == Merge Details == Merge strategy: All the fixes to Maintenance scripts were brought in, but not the changes to active them in crontab that would enable them. Rusty's original change had crontab changes to call maintenance scripts, and also calls to 'p4 unlock -x' as a workround to p4d bugs related to orphanged locks on edge servers. Those bugs are already fixed. Also, adding anything new to cron requires a test suite addition and doc updates. So changes to the template.crontab.combined were ignored. However, a new file was added to the Maintenace folder, sample_cron_entries.txt, to make it easy for folks to see those changes. Rusty's original change had mkdirs.sh changes to generate maintenance.cfg. This change was enhanced during the merge. Rather than overwriting maintenance.cfg (potentially blowing away configuration for other instances), a new section for the new instance is appended to maintenance.cfg when 'mkdirs.sh <instance>' is run. Future considerations: Before adding anything from Maintenance to cron, we need to do the following: * Have mkdirs.sh install the Maintenance folder to the as-deployed structure under /p4/common, i.e. to /p4/common/maintenance, for HMS management compliance. * Add tests and docs for each script called (directly or indirectly). |
||
#1 | 20289 | Russell C. Jackson (Rusty) | Script to convert labels to autoreload labels |