Closed patrikcerbak closed 5 months ago
the help looks great. The only missing part is that queries are XOR -or not? That you can youse only one, but you must use at least one. Or you can really use both?
break for now. Will continue on 6f44fa53c97775ad627c5281e2bbb6d1330b1060 after it
it loks great. It is necessary to fix the consumed exceptiosn (not easy here!!). Good luck!
The consumed exceptions are now logged (printing the stack trace) and it gives the user a warning that an exception occurred.
LGT
I finally implemented dynamic arguments, so instead of --nvr being hardcoded, now you can only use it if you declare it first with
--build-config-find "changelog.xml:nvr:/build/nvr"
for example (but you can define as many arguments as you want).All the build filtering is now done using the ConfigFinder class, as I intended earlier. The finding of the job result (SUCCESS, UNSTABLE, ABORTED etc.) is now also done using the ConfigFinderClass. The default place the tool is looking in is the build.xml file and /build/result xpath, however the user can set it to whatever they want, using the --build-config-find argument, like so:
--build-config-find "myConfig.properties:result:buildResult"
.I also implemented a parsing of JSON config files into the ConfigFinder class.
Last thing, I updated the help message:
What do you think?