At @mikeb's suggestion in the code review, this makes HiddenUsers plural.
This makes the whole changeset a little more invasive than it was before, so please review carefully.
This adds new query arguments to the taskList hub xmlrpc endpoint, and then
makes use of those arguments in koji-web. A new optional configuration value
is added for koji-web: `HiddenUser`, which can be used to specify which user
account should be hidden. This could be useful for deployments that have a
continuous-integration account, the spam from which makes the frontpage
difficult to read.
Unit test cases are also added for some functions of the hub taskList endpoint.
Signed-off-by: Ralph Bean <rbean@redhat.com>
The client CA is only needed to for authentication on the server side,
not for authentication on the client side. Therefore remove it from all
client login code.
Citing from reindent docs:
Change Python (.py) files to use 4-space indents and no hard tab
characters. Also trim excess spaces and tabs from ends of lines, and
remove empty lines at the end of files. Also ensure the last line
ends with a newline.
Citing from PEP 8:
Use 4 spaces per indentation level.
Python 2 code indented with a mixture of tabs and spaces should be
converted to using spaces exclusively.
Don't write string literals that rely on significant trailing
whitespace. Such trailing whitespace is visually indistinguishable
and some editors (or more recently, reindent.py) will trim them.
Also PyLint recommends not to have trailing whitespace on any line.
The code previously would look for a file called extra-footer.html that a koji
admin could override to put some nice extra footer on their koji-web page.
If that file existed, koji-web would read it in verbatim and write it to the
bottom of each served page.
This change enhances that behavior and treats the extra-footer.html file as a
Cheetah template. This way, a koji admin could specify some conditional logic
in the extra-footer file to display this or that thing depending on the dynamic
contents of the page being served.
Note that this is backwards compatible. Static html extra-footer files
already out there in the wild will be interpreted as Cheetah templates and
should be included seamlessly.
This will allow us in Fedora to style system account names differently. For
instance, we can markup the name 'koschei' (our continuous integration bot).
-Dfoo and -Dfoo= mean different things to the JVM, so make sure the format of the parameter on the command-line is carried through to the mvn invocation.
The new "koji chainmaven" command allows Maven builds to be run in depdencency order,
without needing to wait for repo regens. A config file specifies the parameters and
dependencies for each build in the sequence. Each build is launched as soon as all
dependent builds are complete, and is able to reference the output of all of its
dependencies. If the build source URL and parameters match the latest build of the
same package in the destination tag, the build will not be re-run.
