2.4.0

Minor features

• Changed parts of versions are highlighted in bold
• Package's "Dependency changes since last build" is now collapsed, like build's dependency changes

Bugfixes

• Non-cannonical arches would get skipped when used in build_arches configuration variable (#246)
• Fixed dest_tag handling when branching (#245)
• Fixed incorrect wording of tooltip for dependency distance (#257)
• Fixed primary collections treated as secondary in some cases

Other

• unapplied_change table was normalized to be consistent with applied_change
• Multiple test improvements
• Added lots of docstrings

Upgrading from 2.3.1

• Database migration
  • Run alembic -c /usr/share/koschei/alembic.ini upgrade head while the backend services and httpd are stopped

2.3.1

Bugfixes

• Fixed a bug that caused build resolver to mark all builds as having "No dependency changes" (#250)
• Fixed koschei-admin submit-build not working in secondary mode (#249)
• Fixed incorrect build group query in secondary mode (#248)

Upgrading from 2.3.0

• No special action needed

2.3.0

Announcement

• Koschei now requires at least Python 3.5

Features

• Build and repo resolver now support running multiple processes in parallel.
  Each repo resolver can process one collection. Each build resolver can
  process one batch of builds with the same repo_id. (#225)
• Build group is now queried for given repo. This should improve
  resolution accuracy when the group changes. (#242)
• Absolute URL used in bugreport template can now be specified by configuration
  variable frontend.external_url.

Bugfixes

• Don't display "all collections" when there is only one (#233)
• Fix onClick handling on build rows (#235)
• Real build URLs should be urlencoded (#232)
• koschei-admin RPM has undeclared dependency on koschei-backend (#230)
• Fix scheduling in secondary mode (#231)
• Fix default absolute URL used in bugreport template (#239)

Other

• Dropped dependency on six

Upgrading from 2.2.0

• Ensure you're running at least Python 3.5

2.2.0

Announcement

This will likely be the last feature release that supports Python 2. The next release will support Python 3 only and will be built for Fedora 27+ only.

Features

• Logging of user (and admin) actions
  • Actions such as changing package attributes, editing collections etc. are logged into an append-only table.
  • The table references the acting user and the affected package, if applicable
  • There's currently no frontend for the log, it can be accessed using SQL
• Package's tracked status, aka adding/removing package to/from koschei can be toggled in package detail view in scheduler parameters panel
• Untagging and retagging is now reflected in Koschei (#191)
  • Untagged builds are noticed by polling and marked as such
  • Then they're effectively ignored by scheduler and resolver, but still displayed
  • In the frontend they're marked with both text and color
• Genralized authentication configuration to support OpenID Connect
  • Allows to specify the environment variable used to get the username via
    frontend.auth.user_env config key.
• Improved memory limit handling - now considers swapped out memory as well
• Build rows in package detail view are now clickable (lead to build detail)

Bugfixes

• Fix running icon not being displayed in single collection view
• Fix set-priority admin command
• Fix edit-group admin command
• Fix skip resolution attribute being unset after editing groups
• Fix multiple Python 3 incompatibilities

Other

• Removed deprecated PkgDB plugin
• Introduced Travis CI and Codecov.io

Upgrading from 2.1.1

• If you have been using deprecated PkgDB plugin, switch to Pagure plugin
  • See release notes for 2.0.0
• Database migration
  • Run alembic -c /usr/share/koschei/alembic.ini upgrade head while the backend services and httpd are stopped

2.1.0

Features

• Changes of DB schema for representing dependency changes, resulting in:
  • Performance improvements of "affected-by" functionality
  • Considerable reduction of disk size of applied_change table

Bugfixes

• Fix group handling in "Add packages" form (#185)

Other

• Removed deprecated resolver service
• Added alembic subcommand to koschei-admin

Upgrading from 2.0.2

• Database migration
  • Run alembic -c /usr/share/koschei/alembic.ini upgrade head while the
    backend services and httpd are stopped

2.0.2

Bugfixes

• Order builds by started time, not id - should prevent inconsitencies arising when branching
• Fix plugin packaging missing __init__.py file

Other

• Require authentication for long-running queries
• Add memory check to watcher

Upgrading from 2.0.2

• Database migration
  • Run alembic -c /usr/share/koschei/alembic.ini upgrade head while the
    backend services and httpd are stopped

2.0.1

Bugfixes

• Fix pagure plugin installation
• Fix None error in package detail
• Fix no collection disaplyed as current in package detail

2.0.0

Features

• Major user interface redesign (#160)
• Collection branching implemented (#180)
• Pagure plugin for retrieving user's packages (replacement of pkgdb plugin) (#169)

Bugfixes

• Fixes of copr plugin

Other

• Switch to Python 3 for Fedora 27+
• Vagrantfile fixes

Upgrading from 1.11.0

• Database migration
  • Run alembic -c /usr/share/koschei/alembic.ini upgrade head while the
    backend services and httpd are stopped
• As PkgDB was deprecated in Fedora, pkgdb plugin is also deprecated in Koschei
  and will be removed in next release. "My packages" function is replaced by
  pagure plugin. "Autotracking" doesn't have any equivalent in pagure, so the
  feature will no longer available and packages will need to be added through
  koschei.

1.10.0

Features

• Priorities seen in frontend now exactly match what the scheduler sees (#130)
• Show a reason why the package is not scheduled in package detail
• Send fedmsg messages on broken buildroot (#17)
• Allow building from repo_id (#50)

Bugfixes

• Prevent possible duplicate real build inserts
• Fix repo cache LRU

Other

• Priority representation and calculation completely reworked
• "repo" compat field in fedmsg now equivalent to collection name

Upgrading from 1.9.1

• Database migration
  • Run alembic -c /usr/share/koschei/alembic.ini upgrade head while the
    backend services and httpd are stopped

1.9.1

Bugfixes

• Add missing collection arg to "Previous history" link (#131) and to bugreport link
• Fix requires on koschei-common-copr
• Don't assume resolution change existence
• Fix history table layout

Other

• Split resolver service into build_resolver and repo_resolver. Old resolver
  service is still available
• rpmvercmp optimization
• Collection ordering was reversed

Upgrading from 1.9.0

• [optional] You can switch from using resolver service to
  split services - repo-resolver and build-resolver. You can do that by
  stopping and disabling koschei-resolver service and enabling and starting
  koschei-build-resolver and koschei-repo-resolver
• Database migration
  • Run alembic -c /usr/share/koschei/alembic.ini upgrade head while the
    backend services and httpd are stopped