You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
add_filesystem now takes new architectures (orchestrator) and architecture (worker) parameters in preparation for running this plugin in both the orchestrator and worker builds as part of a new plugin arrangement
koji_upload, koji_import and fetch_worker_metadata plugins have been added as part of the effort to allow arch-specific worker builds
Bug Fixes
docker_api now reports errors more readably
sendmail plugin provides correct link to log files
add_labels_in_dockerfile plugin ensures that release and version labels are always set
add_labels_in_dockerfile plugin ensures that aliases for generated labels have always same value
logging output is consistently encoded in UTF-8
fall back to http when connection errors occur while working with insecure registry
show a warning when manifest cannot be converted from v2 to v1 on the registry
slow download speed in fetch_maven_artifacts plugin has been fixed
Improvements
orchestrate_build: in preparation for a new plugin arrangement, if add_filesystem plugin ran for the orchestrator build then provide the resulting Koji task ID to add_filesystem plugin in the worker build
orchestrate_build: metadata_fragment related values are now provided in the annotations for each worker build.
orchestrate_build stores OSBS instance for each worker build in plugin_workspace which can be accessed by using the help function get_worker_build_info
orchestrate_build will ignore worker clusters that cannot be reached when computing their load, instead of causing build to fail
orchestrate_build now uses an optional containers.yaml file from the git repository for exclusion of platforms, as described at http://osbs.readthedocs.io
add_labels_in_dockerfile handles uninspected koji/image-build base images
when determining build failure, containers are inspected for further information
new plugin koji_parent added to ensure parent image has a matching build in Koji.
import_image plugin now ensures that every primary tag is being tracked in ImageStream
koji_tag_build and sendmail plugins attempt to fetch koji-build-id from koji_import falling back to koji_promote
pulp_pull won't run if manifest already has schema 2 ID
Koji builds imported via koji_import will now have media_types metadata to indicate the container image version available.