Releases: containerbuildsystem/atomic-reactor
Releases · containerbuildsystem/atomic-reactor
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
1.6.25.1
1.6.25
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 filesadd_labels_in_dockerfile
plugin ensures thatrelease
andversion
labels are always setadd_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 buildorchestrate_build
: metadata_fragment related values are now provided in the annotations for each worker build.orchestrate_build
storesOSBS
instance for each worker build inplugin_workspace
which can be accessed by using the help functionget_worker_build_info
orchestrate_build
will ignore worker clusters that cannot be reached when computing their load, instead of causing build to failorchestrate_build
now uses an optional containers.yaml file from the git repository for exclusion of platforms, as described at http://osbs.readthedocs.ioadd_labels_in_dockerfile
handles uninspectedkoji/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 ImageStreamkoji_tag_build
andsendmail
plugins attempt to fetchkoji-build-id
fromkoji_import
falling back tokoji_promote
pulp_pull
won't run if manifest already has schema 2 ID- Koji builds imported via
koji_import
will now havemedia_types
metadata to indicate the container image version available.
1.6.24.1
1.6.24
Build JSON API changes
New plugin:
fetch_maven_artifacts
(prebuild):
the plugin is used to fetch Maven artifacts from yaml file and include them in the Dockerfile
Bug Fixes
None
Improvements
orchestrate_build
plugin logs info about worker clusters while choosing between them- All missing labels are reported if
assert_labels
plugin fails add_labels_in_df
- plugin now uses optional equal label aliases
- plugin isn't allowed to fail
- plugin now uses optional info_url_format to add url label
koji
andbump_release
plugins have new param koji_ssl_certs_dir
to use koji auth and ssl_dirsendmail
plugin reworked to use koji information for sending notifications- Better error reporting for push failures
- yaml validation moved from
reactor_config
plugin toutil
module - py2.6 is no longer supported
add_filesystem
plugin is now ready for multiarch filesystem tasks
1.6.23.3
1.6.23.2
1.6.23.1
1.6.23
Build JSON API changes
New plugin:
orchestrate_build
(buildstep)koji_tag_build
(exit)
Bug Fixes
- Fix for possible incorrect tag names for images
- fix a problem in pulp_sync plugin where an image was generated without a namespace (#671)
- print image names in pulp_sync or in pulp_push once - whichever comes later
- add_filesystem: arch is no longer hardcoded
- pulp_push: dockpulp now honors logging level
Improvements
- New plugin
orchestrate_build
was added, will create worker build
(via OSBS methodcreate_worker_build
),
and will as well pass it build_image used for orchestrator - New plugin
koji_tag_build
was added, will tag build only when
build was successfully promoted and its metadata updated
1.6.22
Build JSON API changes
New 'buildstep_plugins' list in ATOMIC_REACTOR_PLUGINS JSON
New plugins:
- reactor_config (prebuild)
- docker_api (buildstep)
Bug Fixes
Parent's environment variables now correctly handle multiple '='
Improvements
- New plugin type "BuildStepPlugin" was added, these plugins are used for actual building of images, this way we are abstracting the build phase, and make it configurable via plugins, there is docker_api plugin which is doing docker image build by default
- test improvements: removed 'test' subcommand from setup.py, removed dead code from test_reactor.py, improved error logging
- pulp_pull can now pull from insecure HTTPS crane