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.
We originally added Vagrant support by tweaking options sent
to the existing RHEV-M and vSphere OVA generation code. This was
a bit of a hack and resulted in confusing filenames.
This adds "vagrant-libvirt" and "vagrant-virtualbox" image types,
passes in the correct options to Image Factory and produces output
files with the conventional ".box" extension and more descriptive
and less confusing vagrant name suffixes.
-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.
This creates a new koji task type and CLI option called
image-build-indirection
This task builds an output image using the Image Factory "Indirection"
plugin
It takes as its input two already built images, either as explicit
task numbers of NVR and arch. It also requires a modified TDL
file as described in the Image Factory source.
The two input images are referred to as the base_image, which contains
content to be turned into another output image, and the utility_image,
which is a full system that will be booted to do the transformation.
The TDL, or "indirection_template" describes the tasks to be performed
inside of the running base image to generate the output.
This feature has the potential to build all of the following types of
images:
Disk Image Builder disk images, built with DIB elements using DIB itself
Live ISO images created using Live Media Creator
Docker layered images built using an arbitrary Docker version and a
Docker base image already built inside of koji
as we publish the raw files on the mirrors we want to be able to request
xz compressed versions of theraw image.
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
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.
Hi *,
When creating new build targets I've messed up a couple of times by not
actually defining the arches in the build tag. Having the koji cli check this
for you seems useful:
Hi,
I've been bitten a few times running "koji wait-repo" that the build I'm
waiting on isn't actually tagged in the right place to get included in the
repo. (Or is blocked, or is typoed etc).
I think koji wait-repo T --build X should actually check that X is the latest
build in T, and warn you if it's not. (Warn not abort in case you're being
clever and running wait-repo at the same time as you build the package)
Here's a patch:
Command like
$ koji download-build --type image --latestfrom guest-rhel-7.0-candidate rhel-guest-image
No image archives available for rhel-guest-image-7.0-20140314.0.el7
used to fail due to .el7 being appended to build that has been searched
for. Image builds doesn't contain the .el7.
