CHANGELOG

This page is meant to detail changes that are made to Kochiku for the benefit of people running their own Kochiku deployments. Since Kochiku is not versioned and users are expected to track the master branch, it is vital to know what has changed when preparing to deploy the latest commit on master.

---

07/17/2014

Moved the test-command into kochiku.yml and added support for uploading additional log files. [#101] (https://github.com/square/kochiku/pull/101)

Added a health page for projects to track flaky tests. [#104] (https://github.com/square/kochiku/pull/104)

Removed support for git notes. [#105] (https://github.com/square/kochiku/pull/105)

06/26/2014

Added an option to have users notified when a build is successful. #89

Changed GitRepo to handle more URL related tasks, including better submodule support. #91

06/13/2014:

Switch from average to median calculation for project build time. #88

Add a whole bunch of caching to the front-end interface. #77

Use git push --force when updating promotion branches. #87

06/11/2014:

Experimental new feature for dynamically scaling up or down kochiku workers. Disabled by default. #86

Update to Carrierwave version 0.10.0. Should be a benign upgrade.

06/03/2014:

Missing database records now trigger 404 pages to be displayed. #83

Introduce polling background job that periodically checks repositories for new commits that have not been built yet. #82

05/29/2014:

Automatically reattempt a build that fails as errored in under 1 minute. #80

Added worker health dashboard to give a quick overview of which build workers may be malfuntioning. #79

05/22/2014:

Change RemoteServer url parsers to allow periods in project names. #78

Update to Rails 4.1 #76

05/20/2014:

Support for aliases/CNAMEs to be specified for a git server. #75

Changes to repository table:

• Renamed repository_name to name
• Add host column (string)
• Add namespace column (string)

05/16/2014:

If a project's remote changes, update the remote of the cached repo in-place. #74

If a build is aborted but all of its build parts are in progress and end up passing, move the build from aborted to passed. #73

05/12/2014:

New Feature: Ability to partition test files using pre-calculated timing information. #72

05/07/2014:

The ref column on the builds table is constrained to 40 characters. Added unique index on ref to DB. #70

04/15/2014:

Remove ability to have Kochiku update a tag instead of a branch after a green build. Tags are not meant to be updated so it was a mistake that this was added in the first place. #67

Remove support for append_type_to_queue in kochiku.yml. This was an undocumented feature that was used to a limited capacity within Square. #68

Remove command_flag column from repositories table and target_name column from builds table. The command flag feature is a relic from Kochiku's beginnings that should have been removed a long time ago. If for some reason you were using it, move your flags into the test_command field or your build script. #69

01/30/2014:

Kochiku migrated from Rails 3.2 to Rails 4. If you deploy with Capistrano, when performing the Kochiku deploy upgrading from Rails 3 to Rails 4 you will run into an asset pipeline + capistrano conflict. Follow the instructions on the Capistrano wiki (Upgrading to Rails 4) for a resolution. The gist of it is that you will need to remove the shared/assets/manifest.yml file and start the deploy again.

Ruby 2.1 is now the recommended Ruby version. Kochiku still works with Ruby 1.9 or 2.0 but at this point Square is testing and deploying it with Ruby 2.1.

/repositories/ID/build-ref was changed to support the Stash Post-Receive Webhook Plugin The response JSON changed in a backwards incompatible way, since it is now possible to trigger multiple builds rather than just a single one. Note that the GET interface suggested in the UI is still valid. This deprecates the custom Kochiku Stash plugin we have been publishing.

01/29/2014:

• The 'auto merge' feature has been renamed internally to merge_on_success which is (hopefully) more descriptive.
• A boolean flag has been added to the repositories table called allows_kochiku_merges. This controls whether Kochiku users can request Kochiku to automatically merge their branch if the tests pass (the aforementioned auto merge feature). The setting can be changed on the repositories edit page.