Atomic-reactor

Build JSON API changes

None

Bug Fixes

- The previous fix for unique tags in Koji metadata was not sufficient

Improvements

None

Build JSON API changes

None

Bug Fixes

- The previous fix for unique tags in Koji metadata was not sufficient

Improvements

None

Build JSON API changes

None

Bug Fixes

- In 1.6.26 orchestrator build annotations were only accurate when Pulp integration was enabled. They are now correct regardless of whether Pulp integration is enabled

- Koji integration: with group_manifests=false in osbs.conf, the Koji output metadata "extra.docker.tags" list included the unique tag in 1.6.26. This was an unintended change from previous releases and has now been reverted.

Improvements

None

Build JSON API changes

None

Bug Fixes

- the Koji build.extra.image.help metadata value was incorrect in 1.6.25 but has now been fixed
- base image is being tagged with a unique label (build ID) to prevent base image to be removed too early having several builds running in parallel on the same node
- Koji integration: if the parent image does not have expected OSBS labels, the Koji check is skipped
- Different values for equal-preference label aliases no longer cause the build to fail
- When Koji and Pulp integration were both enabled, the reported image ID was incorrect because `pulp_pull` ran after `koji_upload`

Improvements

- `orchestrate_build` will pass `is_auto` param to each worker build to help identify autorebuilds.
- python-docker-2.x support has been added
- decoding docker API responses is now performed by docker-python
- `pulp_tag` plugin has been added
- `inject_parent_image` plugin has been added
- `bump_release` plugin correctly increment patched release values
- new `filesystem-koji-task-id` label is set on the OpenShift build by add_filesystem
- new `group_manifests` post-build plugin, for creating grouping image manifests into manifest lists
- new `pulp_publish` exit plugin, intended for orchestrator builds, to handle only the publishing task
- several Pulp plugins have been adjusted to make them able to run in the orchestrator build
- in addition to being a `PostBuildPlugin`, `pulp_pull` is now also an `ExitPlugin`
- `group_manifests` plugin is rendered based on `group_manifests` configuration value
- `koji_import` plugin uploads OpenShift logs from worker builds and orchestrator build
- `koji_upload` plugin no longer uploads OpenShift logs
- `koji_upload` plugin has new arguments:
- `prefer_schema1_digest`, to indicate when schema v1 should still be used
- `platform`, to indicate the platform name to use in filenames for Koji uploads
- `pulp_pull` plugin has a new argument, `expect_v2schema2`, to indicate whether v2 schema 2 image manifests should be expected from Crane
- communication with external HTTP services has been wrapped in a common retry approach

Build JSON API changes

None

Bug Fixes

- `koji_import` saves help annotation as a string instead of json

Improvements

None

Build JSON API changes

- 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.