Releases: containerbuildsystem/atomic-reactor
Releases · containerbuildsystem/atomic-reactor
1.6.20
Build JSON API changes
- New plugin:
add_help
- Removed plugins:
cp_dockerfile
dockerfile_content
This plugin will be removed from the request
squash
:remove_former_image
parameter is removed
Bug Fixes
- Atomic-reactor is now compatible with docker 1.12
add_labels_in_dockerfile
:distribution-scope
label cannot be overwrittenall_rpm_packages
: remove dangling volumes after the container has exiteddistgit_fetch_artefacts
: no longer requiresources
file to be presentexit_koji_promote
: the plugin now correctly authenticates using Kerberosimport_image
: fail after a number of retriespre_koji
: don't crash if the repo or koji tag are misconfiguredstop_autorebuild_if_disabled
: autorebuild is disabled by defaultstore_metadata_in_osv3
: build annotationartifacts
is removed
Improvements
- Show client version from build JSON if available
- Failed build message is now clearer
- Documentation update
- Tests now pass faster as unnecessary pause was removed
- Non-required plugins don't fail the build
- Required plugin errors are stored in annotations correctly
- Additional tests for build cancel and environment variables inheritance
add_filesystem
: koji's filesystem task is canceled if the build is canceledexit_koji_promote
: autorebuild is stored in build metadataexit_koji_promote
: help filename is stored in build metadata if available
1.6.19
Build JSON API changes
None
Bug Fixes
- environment variables set by the parent image are now used when performing environment-variable substitution in the Dockerfile (requires dockerfile-parse >= 0.0.6)
Improvements
- pulp_pull plugin temporarily uses v1 image id
1.6.18
Build JSON API changes
- new plugin:
distribution_scope
- setsdistribution-scope
label - new plugin:
pulp_pull
- fetches image id from pulp after the push - plugins can now be marked as being required for a successful build ('required' keyword)
Bug Fixes
- unknown plugins are now discarded
bump_release
now ignores broken builds- v2 schema 1 manifest ID is used in koji metadata
- build dates don't contain Z postfix - build host timezone is used
- koji build metadata contains an image config if docker 1.10+ is used
- scratch base image builds are now supported. A better error message is displayed
- image is published to pulp once - on
pulp_push
if v1 only is enabled, or duringpulp_sync
- fixed a UnicodeDecodeError in
koji_promote
when build log contained UTF-8 characters
Improvements
- py.test is now executed on
setup.py test
- a warning is printed if the container cannot be removed
bump_release
now ignores broken builds
1.6.17
Build JSON API changes
atomic-reactor now tries to use new-style labels now. See https://github.com/projectatomic/ContainerApplicationGenericLabels/blob/master/README.md and https://github.com/projectatomic/ContainerApplicationGenericLabels/blob/master/vendor/redhat/labels.md
If the base image has old-style tags those would also be set in the produced image.
Bug Fixes
None
Improvements
None
1.6.16
Build JSON API changes
koji_promote
will use first unique_image as the pull spec if no primary_images have been set.pulp_sync
will iterate through all images (unique and primary) to determine which pulp repositories must be published.tag_by_labels
takes an additional, optional, parameterunique_tag_only
. When set, image will only be tagged with unique tag, and not primary tags. Defaults to False.
Bug Fixes
None
Improvements
- Added missing dependencies for tests to spec file
koji_promote
will log koji task ID on failure.
1.6.15
1.6.14
1.6.13
1.6.12
Build JSON API changes
None
Bug fixes
- intermediate docker registry links are not set in annotations if
pulp_sync
plugin is enabled bump_release
plugin now takes component version into consideration
Improvements
- API documentation was updated
- Custom repo urls are supported for base images
1.6.11
Build JSON API changes
- pulp_sync: no longer accepts username and password parameters
- pulp_sync: now accepts optional registry_secret_path, insecure_registry, and pulp_repo_prefix parameters, allowing sync from V2 registry that requires authentication -- note: this requires dockpulp > 1.22
- tag_and_push: registries can now include a "secret" key in their description, which is the path to the Kubernetes dockercfg secret required for pushing to the registry
- bump_release: no longer accepts git_ref, author_name, author_email, committer_name, committer_email, commit_message, or push_url
- bump_release: now requires parameters target (Koji build target) and hub (Koji hub URL)
- tag_from_config: new available plugin
Bug fixes
- plugins whose constructors fail are now handled correctly
Improvements
- pulp_sync is now able to ask Pulp to sync from a V2 registry that requires authentication
- bump_release now uses a Koji hub to discover the latest release of the component and uses that to provide a value for the Release label if missing
- new tag_from_config plugin to add additional tags to the image