Releases: containerbuildsystem/atomic-reactor
Releases · containerbuildsystem/atomic-reactor
1.6.30.1
1.6.30
Build JSON API changes
None
Bug Fixes
- Add digests for prod-type OSBS build to koji build archive extra metadata
- A problem with running in Python 3 was fixed
- Repeated logs from dockpulp are now prevented
- extra.docker.digests is always populated
- release label is set correctly
- chain rebuilds will use latest built image if a parent image is rebuild during the chain rebuild
Improvements
- Removal of unused annotations : logs, rpm-packages
- Removal of parameters: 'module_name', 'module_stream', 'module_version', 'compose_id'
from plugin 'resolve_module_compose', added: 'compose_ids' import_image
is now also anExitPlugin
- Module versioning using ":" as separate is now allowed
pulp_push
plugin copies all v1 layers in a single pulp task- reactor_config plugin reads REACTOR_CONFIG environment variable, and provides methods to accessing its content
- failed chain rebuilds will attach all logs to the notification message, in addition to linking to the logs of the most recent build
- plugins dealing with manifest digests will log more details to improve the ability to diagnosis situations when only one of the two media types appears on a pulp server
- Plugins read environment config from reactor config if available
- Flatpaks: hybrid modularity, container.yaml, package set restriction
orchestrate_build
uses 'reactor_config_override' when creating worker buildsorchestrate_build
allows platform specific overrides in override_build_kwarg()- preparation for rendering plugin configuration separately from the BuildConfig creation (not yet active)
- pulp_pull will retrieve v2 schema 2 manifest lists
- support for content_sets.yaml and pulp repositories in
resolve_composes
- update pulp repos to not automatically publish
- use correct manifest list digest for worker build image
1.6.29.1
1.6.29
Build JSON API changes
- exit plugins marked as required but is missing, will fail build
Bug Fixes
- Remove manifest list from the distribution registry registry after
pulp_sync
group_manifests
: include namespace if it's present in the results- Fix sending the OAuth2 token to ODCS
- Race condition while pulling base image was resolved (#881)
all_rpm_packages
: forces root userkoji_parent
checks label alias
Improvements
- Koji build metadata contains owner and submitter
- Koji build metadata now includes ODCS related information
- jsonschema definition file for
container.yaml
- New
resolve_composes
prebuild plugin to request and use ODCS composes. build_image
for worker is set based on build image in orchestrator OpenShift build
1.6.28
Build JSON API changes
None
Bug Fixes
- OpenShift Build annotations now store the correct value for base-image-id and base-image-name
group_manifest
returns a list ofManifestDigest
objects whengroup=True
Improvements
- Koji build metadata now includes digests-version map
- Flatpak dependencies are now optional
- Koji ssl authentication no longer requires
ca
andserverca
files. - Retry approach has been applied to interaction with worker clusters
- Workaround to retry on 403 for crane requests
- Retry on pull and push from registry
- Retry on git clone operation
manifest-tool
is no longer required- OCI image index support
1.6.27
Build JSON API changes
- New
compare_components
plugin is used to ensure different platforms have a common set of components installed squash
plugin now takessave_archive
to control creation of squashed image archive.- New
remove_worker_metadata
plugin which ensures that worker ConfigMaps are now removed after the build
Bug Fixes
- 'tags' field in Koji build 'output' metadata includes the worker's platform-specific unique tag when
group_manifests=true
- 'repositories' field in Koji build 'output' metadata includes by-digest pull specifications for each pullable object tracked in the registry; for Docker distribution registries this is only the schema 2 digest, but for Pulp this may be both the schema 1 and schema 2 digest
- pulp_pull plugin's image ID from pulling the image is used regardless of platform name; this only applies to installations using Pulp < 2.14
import_image
reads primary tags from either tag_conf or worker builds annotationskoji_promote
saves media types list andkoji_parent_id
to koji metadata same askoji_upload
Improvements
koji_import
will add the ID of parent image's koji build to metadata.- Documentation updates
docker_api
build plugin will provide explanation when build api call fails.- Support for building Flatpaks has been added
add_help
plugin now creates man page header fields from the name and maintainer labels, and the build start timeimport_image
does not explicitly track version-release tags- All requests have timeout set to 10 mins
- Layer sizes are now stored in koji metadata
'build-date'
label format is in UTC- Metadata for Koji builds will indicate whether or not a build is isolated:
extra.image.isolated
- flatpak dependencies are now in a separate file
1.6.26.3
1.6.26.2
1.6.26.1
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
1.6.26
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 afterkoji_upload
Improvements
orchestrate_build
will passis_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 addedinject_parent_image
plugin has been addedbump_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 anExitPlugin
group_manifests
plugin is rendered based ongroup_manifests
configuration valuekoji_import
plugin uploads OpenShift logs from worker builds and orchestrator buildkoji_upload
plugin no longer uploads OpenShift logskoji_upload
plugin has new arguments:prefer_schema1_digest
, to indicate when schema v1 should still be usedplatform
, 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