神刀安全网

Concourse CI Hits 1.0.0

v1.0.0

March 29, 2016

Release Notes

We made it!

This release, although relatively small on its own, is built on years of feedback and iteration. So these notes will be a bit more broad and cover all the things you may have missed since you last checked in on our little CI system.

First off, a huge thanks to Pivotal for sponsoring our project and letting us work on it full-time. Over the past year we’ve had 17 team members rotating through, including 2 designers. Pretty sweet.

With 1.0.0 comes a more rigid release policy on our end. You may see deprecations here and there, so keep an eye out for those via the tags next to each release note, but nothing should change backwards-incompatibly until 2.0.0. We’ll still be releasing at the same cadence as before, so we’ll probably end up at v1.23.0 pretty soon.

Here’s a text-form 80’s montage of all the things you may have missed since v0.17.0, our first release:

  • feature

Build Plans replaced the old style job config.

  • feature

Astandalone binary distribution of Concourse has been introduced. (Download links to the right.)

  • feature

Caching and more efficient artifact propagation: resources fetched by get steps are cached on the workers and efficiently propagated throughout steps in the build plan.

  • feature

A single Concourse can be configured with multiple pipelines dynamically.

  • feature

GitHub auth!

  • feature

Custom resource types can now be added via resource_types in the pipeline, rather than reconfiguring your workers.

  • fix

Lots of performance improvements and optimizations, and resilience to flaky networks.

  • feature

The fly CLI has been entirely rewritten and is much more consistent in UX.

  • feature

Concourse knows its own version number and will warn you if your CLI is out of date.

  • feature

Tasks have explicit inputs and outputs , making artifact consumption and production a lot easier to follow.

  • feature

A new color scheme that’s more colorblind-friendly.

  • feature

A whole bunch of improvements tocore resources.

…and now for the actual 1.0 release notes, if you’re upgrading fromv0.76.0:

  • feature

  • breaking

The Concourse BOSH release is now built for BOSH 2.0. You will need a recent director to upgrade. ConsultClusters with BOSH for information on the new BOSH 2.0 deployment scheme.

  • fix

Resources backed by a resource type defined in resource_types will now periodically check for new versions of the resource type and use the latest one for checking. Previously the same container would be reused forever even if a new version of the resource type was released.

  • feature

We’ve added aria-label attributes to all buttons in the UI, which should improve accessibiltiy for folks using screen readers. Still a ways to go overall, but this is a start.

  • fix

Lots of dots in sequence in build output will now word-wrap once again.

  • feature

The BOSH release can now be configured to use GitHub enterprise endpoints for GitHub auth.

  • fix

Connections fromATC to Baggage Claim will now retry on connection errors.

  • fix

Fixed an issue where volumes would "expire" even though a build was still using them. Did a bunch of refactoring and now it should all be pretty airtight.

  • fix

We’ve fixed a goroutine leak on the ATC which would occur every time image_resource was used.

Downloads v1.0.0

Concourse Binaries

BOSH Releases

v0.76.0

March 23, 2016

Release Notes

  • fix

v0.75.0 introduced a client-side limit of 64 connections to the database, which no one would ever hit so we didn’t bother putting it in the release notes. Then a bunch of people with large deployments hit it and their Concourse went cold. Sorry.

We’re removing the limit and are going to do some investigation into the ATC’s connection pool characteristics before considering adding it back.

  • feature

The pipelines sidebar is now scrollable. Some of y’all had a lot of them and got tired of buying larger monitors.

  • feature

Jobs can now have their manual triggering disabled, via disable_manual_trigger .

  • feature

The BOSH deployment resource now supports BOSH 2.0 manifests . Previously it would explode instead.

  • feature

The ATC can now be configured to authenticate against a GitHub Enterprise deployment, thanks to @aequitas !

  • fix

Cleaned up some internals to fix the root cause some noisy but harmless log lines ( failed-to-lookup-ttl ).

  • feature

The Semver resource now supports OpenStack Swift as a storage backend, thanks to @ChrisPRobinson !

  • feature

The Time resource can now be configured to only yield new timestamps on certain days of the week, thanks to @joek !

  • feature

fly learned the rename-pipeline command, thanks to @zachgersh !

  • feature

The Docker Image resource should now be more durable to flaky Docker registries, by retrying with exponential backoff on network errors or 5xx responses.

  • feature

The BOSH deployment resource now downloads the deployment manifest when used as a get .

  • fix

Previously the Pool resource would require you to specify retry_delay in nanoseconds, which was a bit silly. It now accepts Go duration format, e.g. 30s .

  • fix

The Tracker resource now correctly handles rejected stories by only delivering them if a new commit has been made after they were rejected.

Downloads v0.76.0

Concourse Binaries

BOSH Releases

v0.75.0

March 9, 2016

Release Notes

  • feature

  • deprecation

The Semver resource now creates a file called version containing the version number, making it consistent with other resources that provide a version.

We still create number for backwards compatibility, but you should switch.

  • feature

  • deprecation

Specifying both file and config on a task step is now deprecated. You should receive warnings when running set-pipeline and when running a task that specifies both.

Instead, you should be specifying params , input_mapping , and output_mapping .

  • feature

The Fly CLI and the web UI now know their own version! We probably should have done this years ago. So fly -v now works instead of printing a shrugging emoticon, and the web UI now has the version at the bottom right (it even live updates, for all your CI monitors out there).

In addition, fly will print a warning if the versions are slightly out of sync (patch release), and straight up prevent itself from running if they’re significantly out of sync (i.e. minor or major).

  • fix

Tagged workers are now supported by image_resource .

  • feature

The duration that containers stick around for after finishing is now configurable via new atc.retention.* BOSH properties (and corresponding flags to the ATC).

  • feature

intercept now sorts its container list, which should aid in frustration with finding the container to intercept.

  • feature

containers now shows the TTL (as we’ve configured it) and validity (actual expiration, which counts down to 0) for each container. This will be useful to know which ones are sticking around because they failed, and which ones are sticking around because of a build that’s running too frequently.

  • feature

fly learned the abort-build command, thanks to a pull request from @zachgersh .

  • feature

fly learned the trigger-job command, thanks to a pull request from @aminjam .

  • feature

The BOSH deployment resource now supports deploying to a director using UAA client ID/secret for auth.

  • feature

We’ve bumped the version of Buildroot that many of our resources are based on, which should bring in updated CA certificates and other miscellaneous things.

  • fix

Previously resources that had params involving lists of objects would cause Concourse to blow up instead of working. It should now work.

Downloads v0.75.0

Concourse Binaries

BOSH Releases

v0.74.0

February 26, 2016

Release Notes

  • feature

You can now configure resource types in your pipeline rather than redeploying your workers with additional resource types. This should make it much easier to use thecommunity resources that people have built!

  • feature

Autoscroll on a build page is back and is now implemented in a way that doesn’t kill the browser when you have many build events.

  • feature

If the Docker image you specify in the image_resource section of your task has a custom user then we will now respect that when running the task. This user will also be used when hijacking in to a build container.

  • feature

Hijacked connections will no longer cause connection timeouts at interim load balancers if there is no input or output.

  • feature

The pipeline graph rendering now has large portions of the computation cached. This should provide a significant speedup and decrease in CPU load when viewing a pipeline.

  • feature

We’ve made some tweaks to the ATC’s build scheduling that should fix "deadlock" scenarios with serial groups.

Previously, if a pipeline of "A -> B -> C" had all 3 jobs in a serial group, and the builds were enqueued in order of C, B, then A (manually), nothing could ever run, as the scheduling was based on the order of the builds being enqueued, and C would never be satisifed. This is now fixed by collecting inputs and then scheduling only once they’re available, so that C never gets scheduled, and so A is able to be scheduled, followed by B, and then C.

  • fix

The icon font that was broken in Safari by v0.73.0 are now unbroken by v0.74.0.

  • fix

Interrupting a fly execute that was fetching outputs will no longer panic if you cancel it in the middle.

  • feature

If you try and trigger a build while you are not logged in then we’ll now redirect you back to the build page you were on rather than the main pipeline page.

  • feature

The Pool resource will now ignore in-place modifications when working out if a log aquisition is still valid.

  • feature

The Fly CLI will now print the target it will be interacting with at the start of every command.

  • breaking

The Fly CLI default value of the -t flag has been removed. If you’re using the VirtualBox distribution then you’ll need to start logging in and supplying a target. This is to get people in this habit before they progress to a bigger deployment.

  • feature

The Fly CLI has a more sensible timeout and a better error message if it cannot reach the targeted Concourse.

  • feature

We bumped to Go 1.6. You should see absolutely no change.

Downloads v0.74.0

Concourse Binaries

BOSH Releases

v0.73.0

February 18, 2016

Release Notes

  • feature

  • breaking

The destroy-pipeline command now runs much quicker. Unfortunately to implement this there’s a massive database migration. Expect anywhere from a few minutes of downtime up to a few hours when you upgrade to this version, depending on how many builds you have and how chatty they are. Sorry about that.

There is no way of predicting how long this migration may take for your instance. It depends on the chattiness of your builds and the performance of your database. For a rough approximation: running the migration on the Concourse team’s server took 20 minutes to migrate 13 million build events.

You can find out how many build events you have by running the following query against your Concourse database:

SELECT relname, n_live_tup FROM pg_stat_user_tables WHERE relname = 'build_events';

The root of the issue is the amount of data in the build_events table. If you don’t have many build logs then then you can probably just upgrade and not worry about the rest of this. If the upgrade is going to take too long then you’ll need to find some way to reduce the rows in that table.

Before you delete any data from the system you should make sure to take a backup of your database and make doubly sure you can restore it while blind-folded and upside-down in case anything goes wrong.

If you don’t care about your old build logs then you can simply run TRUNCATE build_events; before upgrading and the migration will be quick and painless.

Many of you probably do care about your build events but maybe only those which were created in the past X months. If this sounds like a good idea then have I got the SQL query for you! Run this against your Concourse database (change the X to the number of months you’d like to keep):

DELETE FROM build_events WHERE build_id IN (   SELECT builds.id   FROM jobs JOIN builds ON jobs.id = builds.job_id   WHERE builds.end_time < NOW() - INTERVAL 'X month'   ORDER BY builds.id );

This query may take a while to execute but your Concourse can be online the entire time that it is running.

If you want to keep all of your build logs and have a fast migration then I’m sorry, I can’t help you. :( Maybe upgrade over a weekend?

  • breaking

The Docker Image resource no longer produces the docker save d image by default. This is to reduce disk usage when using the resource as an image_resource . You must now pass save: true as part of params on the get step to produce the image file.

  • feature

Inputs to jobs that are not configured to trigger the job when new versions appear will now be rendered with a dashed line. This makes it easier to see which resources automate the pipeline flow, and which jobs are only ever manually triggered.

  • feature

A pending build will now indicate why it’s pending, via a checklist that appears at the top of the build output. (Yay!)

  • breaking

The theme selector is gone. So are all but one of the themes. This new theme is the product of our research and your feedback. I’m confident that it’s perfect in every way. But let us know if you have any major problems with it.

  • fix

Improved the caching of resources used for image_resource . Previously if the same version was fetched multiple times on the same worker, we’d keep all of them around so long as they were the latest version. We’ll now only keep one.

  • feature

The destroy-pipeline command learnt the -n option which when used will not ask you to confirm the deletion of the pipeline. Useful for scripts. Dangerous for users.

  • fix

The Docker Image resource no longer worked for images configured with ENTRYPOINT s as ofv0.72.0, and ended up running whatever the entrypoint was, with our internal binary tool as an argument. It now works again. Our bad.

  • fix

The GitHub release resource would have issues when fetching artefacts from S3 via GitHub when using an access token. It no longer has these issues.

  • feature

The Docker Image resource now supports a dockerfile parameter for specifying a path to the Dockerfile to use.

  • feature

The Git resource now supports producing annotated tags via the annotate parameter.

  • feature

The Git resource now supports checking for tag patterns like *-production via the tag_filter source configuration.

  • feature

The Git resource now includes git lfs .

Downloads v0.73.0

Concourse Binaries

BOSH Releases

v0.72.1

February 8, 2016

Release Notes

  • fix

Fixed a bug that would cause containers used by the new image_resource not to be released.

  • fix

Removed a uniqueness constraint on the database that checked a huge number of columns which caused PostgreSQL to error for certain pipelines.

Downloads v0.72.1

Concourse Binaries

BOSH Releases

v0.72.0

February 6, 2016

Release Notes

  • feature

  • deprecation

We’ve added a new way of specifying the image for a task. You can now use image_resource which will use Concourse resources to pull the image down.

For example:

image: docker:///ubuntu#14.04

would now become:

image_resource:   type: docker-image   source:     repository: ubuntu     tag: 14.04

If those keys look familiar that’s because they’re the same ones you would specify if you were defining a resource in your pipeline. This means that because the Docker Image resource supports private repositories you can now use private repositories for your task images. There are more details in theTasks section of the documentation.

Further improvements to this feature are coming soon!

  • feature

  • breaking

Resources now have access to the external URL of the Concourse that they are associated with in the environment variable ATC_EXTERNAL_URL .

The property atc.external_url is now required for ATC to start up.

  • breaking

In order for a task to make something for a later step in the plan it now must use outputs . Previously the task’s entire working directory was made available if outputs were not configured, which led to more network traffic than necessary if you didn’t intend for the task to actually propagate anything to later steps.

  • feature

We now validate task configuration at the start of a task. Sneaky things like typos and overlapping inputs and outputs are now hard errors.

  • feature

The new default theme concourse is the culmination of our work on color schemes. It will soon take its place as the one and only color scheme.

If you’ve been changing your theme around, make sure to manually switch to the concourse theme to check it out, otherwise it’ll stick with whatever scheme you last selected.

  • feature

Failed jobs are now displayed with an additional border and a symbol above the column that they are contained in. This change along with the improved color scheme should help the 315,000,000 potential and current Concourse users around the globe who are color blind.

  • feature

The atc.publicly_viewable flag now applies to the API endpoints as well as the web interface. There was no secret information exposed by the API but potentially sensitive things like job names for unannounced projects were there.

  • fix

We fixed the bug that would show your entire pipeline in the diff when uploading changes to your pipeline.

  • fix

New line characters in resource metadata output are now preserved again when viewing them in the web build view.

  • fix

If a job has both pending and running build we will now show the running build animation on the dashboard rather than the less interesting pending animation.

  • fix

If you view a job or build in a paused pipeline then the top bar on the page will be blue again.

  • feature

fly now presents a far more helpful error message if you’re not logged in.

  • feature

The pipeline layout algorithm has changed to draw resources at an appropriate height so that more of the lines are straighter.

  • fix

The list of containers returned when you try and hijack is now correctly filtered to the build number you ask for.

  • fix

The ATC doesn’t panic anymore if the database disappears in the middle of a build. It still gets pretty mad though so try and keep your database disappearing to a minimum.

  • feature

The Tracker Resource now understands variations on the word "completed" when scanning commit messages.

  • fix

ATC will now handle if you supply an atc.external_url with a trailing slash rather than not letting GitHub users log in. A significant improvement if I do say so myself.

Downloads v0.72.0

Concourse Binaries

BOSH Releases

转载本站任何文章请注明:转载至神刀安全网,谢谢神刀安全网 » Concourse CI Hits 1.0.0

分享到:更多 ()

评论 抢沙发

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址
分享按钮