Lines Matching +full:point +full:- +full:to +full:- +full:point
29 description="%(prog)s will process the plug-in packages passed to it."
30 + " A plug-in package is essentially a directory containing"
31 + " one or more call point programs. Each of these call point"
34 + " (described below). For each plug-in package passed,"
36 + " point program in the plug-in directory. If it is found,"
38 + " caller to set any environment variables needed by the call"
39 + " point programs.\n\nAfter each call point program"
42 + " failed_plug_in_name: <failed plug-in value,"
44 + "<shell return code value of last call point program - this"
46 + " that if a call point program returns a value it will be"
49 + " reserved for errors in calling the call point program"
50 + " rather than errors generated by the call point program.>",
52 prefix_chars="-+",
64 "--call_point",
67 help="The call point program name. This value must not include the"
68 + ' "cp_" prefix. For each plug-in package passed to this program,'
70 + " the plug-in directory."
75 "--allow_shell_rc",
77 help="The user may supply a value other than zero to indicate an"
78 + " acceptable non-zero return code. For example, if this value"
79 + " equals 0x00000200, it means that for each plug-in call point that"
81 + " above regarding left-shifting of return codes."
86 "--stop_on_plug_in_failure",
90 help="If this parameter is set to 1, this program will stop and return "
91 + "non-zero if the call point program from any plug-in directory "
92 + "fails. Conversely, if it is set to false, this program will run "
93 + "the call point program from each and every plug-in directory "
95 + "you'd want to run all plug-in call points regardless of success "
100 "--stop_on_non_zero_rc",
104 help="If this parm is set to 1 and a plug-in call point program returns "
105 + 'a valid non-zero return code (see "allow_shell_rc" parm above),'
108 + " where the caller wishes to stop processing if one of the plug-in"
109 + " directory call point programs returns a special value indicating"
111 + ' calling some kind of "check_errl" call point program. Such a'
112 + " call point program might return a 2 (i.e. 0x00000200) to indicate"
114 + " therefore to be ignored. That being the case, no other"
115 + ' "check_errl" call point program would need to be called.'
120 "--mch_class", default="obmc", help=mch_class_help_text + default_string
139 # Convert to hex string for consistency in printout.
146 Run the call point program in the given plug_in_dir_path. Return the following:
147 rc The return code - 0 = PASS, 1 = FAIL.
153 …call_point The call point (e.g. "setup"). This program will look for a progr…
154 … named "cp_" + call_point in the plug_in_dir_path. If no such call point
156 …allow_shell_rc The user may supply a value other than zero to indicate an accepta…
157 … non-zero return code. For example, if this value equals 0x00000200, it
158 … means that for each plug-in call point that runs, a 0x00000200 will not
159 … be counted as a failure. See note above regarding left-shifting of
171 # No such call point in this plug in dir path. This is legal so we return 0, etc.
175 "------------------------------------------------- Starting plug-"
176 + "in -----------------------------------------------"
181 stdout = 1 - quiet
201 "auto_status_file.py --status_dir_path="
203 + " --status_file_name="
205 + " --quiet=1 --show_url=1 --prefix="
207 + " --stdout="
223 # Shift to left.
231 # Use tail to avoid double-printing of status_file_url.
233 "tail -n +2 " + status_dir_path + status_file_name,
239 "------------------------------------------------- Ending plug-in"
240 + " -------------------------------------------------"
286 "Stopping on non-zero shell return code as requested"
292 print_error("At least one plug-in failed.\n")