v0.36.0

Fixed an issue in the gate component’s BOSH templates, which only
seemed to affect building the Packer box.

v0.35.0

There was a little delay in cutting this release as the laptop high
performance build cluster we use to build the Packer boxes was
decomissioned as we switched over to new hardware.

• Workers can now advertise the platform that they support as well as
  additional tags that can influence the placement of builds.

  Today’s build configs will have to start specifying an explicit
  platform. See [missing] for more information. The main takeaway is
  that you’ll need to add platform: linux to all of your
  build.ymls.

  For more information on configuring additional workers, see [missing].

• The scheduler semantics have been simplified which has the main effect
  of making sure that disabled resources are not used in manually
  triggered builds.

• You can now download a compatible fly from ATC. Look for the links
  in the bottom right of the main page. The new fly sync command can
  be used to synchronise the version of fly with the targetted ATC.

• The UI has been spruced up with some little icons. Let us know what
  you think.

• We’ve upgraded Go to version 1.4.2 inside the release. You shouldn’t
  notice any difference with Concourse but this should give you a warm
  fuzzy feeling inside.

v0.34.0

• Added a GitHub Releases resource. It can pull down and push up
  multiple blobs, and tracks releases via their version. For more
  details, see its
  README.
• The navigation bar is now present on every page.
• Upgraded to Consul v0.5. This should fix cases where the workers would
  lose contact with the ATC and never rejoin.
• Fixed a panic in the ATC that would happen every time a job with no
  build configuration finished.
• Added missing merge strategy binaries to the Git resource; this allows
  the rebase option to work in more cases.

v0.33.0

• Now works with the latest Garden Linux again.
• Reworked the build view’s ansi parsing, which now uses an external
  library. This fixes some rendering issues (e.g. long swaths of text in
  a single color now preserve the color for the whole region).

v0.32.0

• The faux ’back’ button on the build view page has been replaced with
  the navigation bar from the main page.

• The ATC’s logging level can be reconfigured via the API. Getting and
  setting it is done via GET and PUT to /api/v1/log-level. Valid
  values are debug, info, error, and fatal.

  Additional logging has been added at the debug level, now that it
  can be kept quiet by default.

• Fixed a bug that could cause pending builds of serial jobs to never
  run. Upgrading prevents this and will fix any stuck jobs.

• The main page is now durable to network errors, and will continue to
  update.

• Pending builds can now be aborted again.

v0.31.0

• Fixed a bug that caused containers not to be released after builds
  completed. This caused defunct containers to build up on the box and
  give Garden a run for its money.

• We’re tracking Garden master again. It’s a good day.

• The Docker image resource would fail to download images over 1G in
  size. Since some people decide to put way too much junk in their
  images we’re increasing this to 10G. Don’t make us do it again.

  Busybox, people. Busybox.

• Outputs which didn’t have any metadata no longer visually hang
  forever. Now you can see that sweet Pivotal Tracker resource output
  again.

v0.30.0

• Fixed a bug that caused containers not to be released after builds completed. This caused defunct containers to build up on the box and give Garden a run for its money.

• We’re tracking Garden master again. It’s a good day.

• The Docker image resource would fail to download images over 1G in size. Since some people decide to put way too much junk in their images we’re increasing this to 10G. Don’t make us do it again.

  Busybox, people. Busybox.

• Outputs which didn’t have any metadata no longer visually hang forever. Now you can see that sweet Pivotal Tracker resource output again.

v0.29.0

• Individual resource versions can now be disabled by clicking the
  toggle switch on the resource pages. This is useful if there is a
  broken or pulled input resource version that you want to ignore in
  automatically triggered builds.
• The subtle pulsing animation that represented a running build has been
  replaced by a more obvious effect.
• If hijack-ing running builds isn’t your thing you can now run
  fly intercept to achieve the same thing.
• The S3 resource output metadata now includes the URL of the published
  file. This only applies to public buckets.

v0.28.0

Removes the Turbine component. See v0.27.0’s release notes.

Note that the deployment manifest has changed once again, this time to
remove the turbine job. See the example
manifests.

If you skip v0.27.0, any builds running during the Concourse upgrade
will be orphaned. If you’re upgrading from v0.27.0 everything should be
fine.