= Release Notes

=== Version 2.1.13
Bug fixes:
* Large run interval for application schedule causes argument out of range error

Features/Changes:
* Cleanup script to remove data from the Naf schema
* aws-sdk and yajl-ruby gems added in naf.gemspec
* Html escape characters in log display instead of log files
* Scripts tab renamed to Applications
* Ability to download job logs
* Ability to re-enqueue finished/errored/terminated job
* Send Datadog metrics on runners

=== Version 2.1.12
Bug fixes:
* Logical::Naf::ConstructionZone#enqueue_application missing application_schedule parameter

=== Version 2.1.11
Bug fixes:
* Runner behaves correctly when it tries to delete a non-existing running job
* Adding application schedule prerequisites works correctly
* Log display outputs custom message when record id is not present

Features/Changes:
* Only show affinities associated with machines that are not deleted
* Runner will cleanup other runners after they are dead
* Machine manager updates machines row if server address or server name match
* Improvements on naf runner script

=== Version 2.1.10
Bug fixes:
* LogArchiver correctly removes files and directories
* Disabled machine is highlighted in red
* Custom validation for machine marked as enabled and deleted
* UI links behave correctly if the engine's mount path is different than '/job_system'

Features/Changes:
* Improved memory management
* Removed machine log display

=== Version 2.1.9
Bug fixes:
* Logical::Naf::ConstructionZone doesn't properly propagate affinity parameters

=== Version 2.1.8
Bug fixes:
* Removed check for signed message. Encrypted data generated by ActiveSupport::MessageVerifier is different depending on the ruby version.

=== Version 2.1.7
Bug fixes:
* Boss#enqueue_command had the first two parameters switched
* Boss#enqueue_n_commands referenced a machine object, but that object did not exist in the scope
* Boss#enqueue_n_commands called job_affinity_tabs on a job when it should be calling historical_job_affinity_tabs
* Foreman#limited_by_run_group? checked the affinity_classification_name of an affinity, but did not check if the affinity was null
* Job exit status always set to 0, even after the job errors
* Unnecessary 'open4' require statements
* Deleted application still runs if it has an enabled schedule
* LogArchiver did not delete empty folders

Features/Changes:
* Created a log archival queuer script
* Created Api Authenticator for logs

=== Version 2.1.6
Bug fixes:
* Historical jobs application_schedule_id was not getting set, causing the runner to constantly queue applications.
* Pagination of application schedules on the index page was not properly working.
* When mouse hovered over the application schedule on the applicaiton show page, it did not show a detailed information about the schedule.

Features/Changes:
* Included application name when editing an application schedule

=== Version 2.1.5
Bug fix:
* The code to manually add jobs/applications/schedules to the queue (::Logical::Naf::ConstructionZone::Boss) had an unecessary parameter that got passed into a call to create a job, thus raising an exception.

=== Version 2.1.4
Bug fix:
* The Runner was using ruby Threads to write the logs of each running script. There was a specific script that caused write blocks and raised an EPIPE exception. The code is no longer using ruby Threads.

=== Version 2.1.3
Bug fix:
* Migrations would fail if run all at once, because it did not consider the existence of the Janitor's Application Schedule. It would then fail, because run_interval is null, run_start_minute is dropped, and a not null constraint is set on run_interval.

=== Version 2.1.2
Bug fix:
* Rescue EAGAIN and EWOULDBLOCK exceptions and log them.

=== Version 2.1.1
Bug fix:
* When marking a machine down, it logs the id of the machine doing the action. But if this machine does not have an associated row in naf.machines, it raises an exception.

=== Version 2.1.0

Featurs/Changes:
* Run interval styles determines the type schedule interval (daily, hourly, run, constant)
* Application can have many schedules
* Application run group quantum specifies the number of jobs queued during a schedule
* UI changes
* Ability to output Jobs/Runner logs from a script

=== Version 2.0.0

Features/Changes:
* New logging system
* Removed compatibility with Papertrail
* UI changes
* Resizable table columns
* Script handles runner commands

=== Version 1.0.0

Features/Changes:
* Three table queue (Historical, Running, Queued)
* Job tags (system, custom visible/invisible)
* Papertrail logging for Jobs and Machines
* CPU/Memory control of Jobs
* Environment specific log configuration
* Enqueue switch for application_schedules
* Machine runner management
* Killed jobs marked as terminating/terminated
* Updated display of timestamps (Started At, Finished At, Run Time) for Jobs
* Fixed buttons to add Jobs to the Queue
* Jobs index page is automatically refreshed

=== Please find up-to-date information on Naf here: {Naf Wiki}[http://www.github.com/fiksu/naf/wiki]