0.41

Minimum required atomic-reactor version

• 1.6.25

Default arrangement version is 3.

API changes

• BuildResponse now provides method 'is_cancelled()'
• PodResponse now provides method 'get_failure_reason()'
• create_prod_build method is now deprecated and will be removed in the future; create_orchestrator_build is now the preferred method of submitting builds
• orchestrate_build plugin is now rendered to pass artifacts_allowed_domains to worker builds
• New koji_parent plugin has been added to latest arrangement

Build JSON changes

• New arrangement version 2 added: add_filesystem runs in both the orchestrator and worker builds
• New arrangement version 3 added: koji_upload runs in worker builds; fetch_worker_metadata, koij_import, koji_tag_build, sendmail run on orchestrator build. koji_promote plugin has been disabled.

Bug Fixes

None

Improvements

• When creating ConfigMaps, data is serialized in JSON to allow nested JSON documents. In addition, the get_data method of ConfigMapResponse automatically deserializes data.
• Support has been added for the new 'koji_upload' plugin
• CLI build sub-command takes koji-upload-dir parameter
• Allow skipping errors when builder is being backed up / restored
• Build summary is displayed once complete
• yum_proxy value is passed to worker builds
• image change triggers are not set, if autorebuild has been disabled in repo configuration
• if autorebuild is enabled and Dockerfile defines "release" label, build is prevented from starting

0.40.1

Minimum required atomic-reactor version

1.6.18

koji_promote and orchestrate_build may be incompatible with atomic-reactor < 1.6.24

API changes

None

Build JSON changes

None

Bug Fixes

• Switched order ofbump_release and add_labels plugins, so the 'release' value exists even for baseimages

0.40

Minimum required atomic-reactor version

1.6.18

koji_promote and orchestrate_build may be incompatible with atomic-reactor < 1.6.24

API changes

• Added support in config for:

  • low_priority_node_selector
  • node_selector.platform
  • artifacts_allowed_domains
  • equal_labels
  • info_url_format

• 'git_branch' param is required in 'create_*_build' methods, otherwise build fails

• When worker build gets 'release' parameter, it will add 'release' label,
  and bump_release won't be used in worker build

• New API 'create_config_maps' to create a config map with arbitrary content. Some atomic-reactor plugins, e.g. koji_upload will use that

• 'create_prod_build' is deprecated in favor of 'create_orchestrator_build'.
  The function is not guaranteed to work in next releases

• CLI:

  • a new --arrangement-version option, to set version of inner template to use
  • a new --source-registry-uri option, to set source registry for pulling parent image

Build JSON changes

• Pass 'equal_labels' and 'info_url_format' from configuration to 'add_labels_in_df' plugin

Bug Fixes

• correctly reset RNG seed to work with forking apps, e.g. koji builder

Improvements

• Triggers are removed from BuildConfig if omitted in prod.json
• imageStream and imageStreamTag check would log errors as debug info
• Allow empty triggers in prod.json
• Support old setuptools on el7

0.39.2

Minimum required atomic-reactor version

1.6.18

koji-promote and build_orchestrate may be incompatible with atomic-reactor < 1.6.23.3

API changes

None

Build JSON changes

None

Bug Fixes

get_build_logs API method now returns encoded bytes

Improvements

None

0.39.1

Minimum required atomic-reactor version

1.6.18

API changes

None

Build JSON changes

None

Bug Fixes

Removed duplicated json decoding.

Improvements

None

0.39

Minimum required atomic-reactor version

1.6.18

API changes

None

Build JSON changes

None

Bug Fixes

• Further fixes relating to handling connections being closed by the server

Improvements

None

0.38

Minimum required atomic-reactor version

1.6.18

API changes

None

Build JSON changes

None

Bug Fixes

• Catch connection close exceptions from python-requests and httplib in order to reconnect

Improvements

None

0.37

Minimum required atomic-reactor version

1.6.18

API changes

None

Build JSON changes

None

Bug Fixes

None

Improvements

osbs-client now uses python-requests instead of pycurl in order to improve task watching and SSL support

0.36.1

Minimum required atomic-reactor version

1.6.18

API changes

None

Build JSON changes

• a new 'config_kwargs' param is added

Bug Fixes

None

Improvements

• parameters used as Configuration are passed to the ochestrate_build plugin

0.36

Minimum required atomic-reactor version

1.6.18

API changes

• new method create_orchestrator_build for creating orchestrator build

• added support in config for:

  • can_orchestrate (enables using orchestrator)
  • arrangement_version (default version of inner template to use when creating orchestrator build)

• CLI: a new --orchestrator option for build to create orchestrator build
  which requires argument:

  • --platforms (name of each platform to use)

• CLI: a new --worker option for build to create worker build
  which requires arguments:

  • --platform (platform name to use)
  • --release (release value to use)

Build JSON changes

• For orchestrator builds, there are new build json files,
  which have same function as the ones already used, only these are specific for
  orchestrator or worker builds.

  • Based on prod.json there are worker.json and orchestrator.json.

  • Based on prod_inner.json there are orchestrator_inner:1.json and worker_inner:1.json,
    where 1 is arrangement_version from configuration file, to specify default version.

  • Based on prod_customize.json there are orchestrator_customize.json and worker_customize.json.

Bug Fixes

• A typo in the spec (#547)
• Retry on conflict updating labels/annotations (#541)
• avoid dependency problems when installing using pip (#537)
• pass git_branch to builds if available (#536)
• token is considered a valid auth method (#533)

Improvements

• when running orchestrator build, build_image specified in osbs.conf is passed
  to the worker build (worker will use same build_image as orchestrator)

• unique_tag_only configuration is now ignored,
  specifying "scratch = true" will always only tag built image with unique tag