Skip to content

@vito vito released this Oct 31, 2019

🔗 feature

  • We've introduced a components table in order to better synchronize all the internal processes that run on the web nodes.

  • This should help reduce the amount of duplicated work (when running more than 1 ATC), and decrease the load on your database.

  • There is no configuration required to take advantage of these new improvements.

🔗 feature, breaking

  • The CloudFoundry auth connector, when configured to authorize users based on CF space membership, will now authorize space auditors and space managers in addition to space developers. This is a breaking change as any teams with CF space-based configuration may grant access to users that they wouldn't have before. #4661

🔗 feature, breaking

  • All API payloads are now gzipped. This should help save bandwidth and make the web UI load faster. #4470

🔗 feature

  • @ProvoK added support for a ?title= query parameter on the pipeline/job badge endpoints! Now you can make it say something other than "build". #4480
    badge

🔗 feature

  • @evanchaoli added a feature to stop ATC from attempting to renew Vault leases that are not renewable #4518.

🔗 feature

🔗 feature

  • API endpoints have been changed to use a single transaction per request, so that they become "all or nothing" instead of holding data in memory while waiting for another connection from the pool. In the past, this could lead to snowballing and increased memory usage as requests from the web UI (polling every 5 seconds) piled up. #4494

🔗 feature

  • You can now pin a resource to different version without unpinning it first #4448, #4588.

🔗 fix

  • @iamjarvo fixed a bug where fly builds would show the wrong duration for cancelled builds #4507.

🔗 feature

  • @pnsantos updated the Material Design icon library so now the concourse-ci icon is available for resources 🎉 #4590

🔗 fix

  • The fly format-pipeline now always produces a formatted pipeline, instead of declining to do so when it was already in the expected format. #4492

🔗 fix

  • Fixed a regression when running fly sync it shows warning of parsing Content-Length and progress bar not showing downloading progress. #4666

🔗 feature

  • Concourse now garbage-collects worker containers and volumes that are not tracked in the database. In some niche cases, it is possible for containers and/or volumes to be created on the worker, but the database (via the web) assumes their creation had failed. If this occurs, these untracked containers can pile up on the worker and use resources. #3600 ensures that they get cleaned appropriately.

🔗 feature

  • Add 5 minute timeout for baggageclaim destroy calls. #4516

🔗 feature

  • Add 5 minute timeout for worker's garden client http calls. This is primarily to address cases such as destroy which may hang indefinitely causing GC to stop occurring. #4467

🔗 fix

  • Transition failed state containers to destroying resulting in them being GC'ed. This ensures that if web's call to garden to create a container times out, the container is subsequently deleted from garden prior to being deleted from the db. This keeps the web's and worker's state consistent. #4562

🔗 fix

  • Previously, if a worker stalled, the atc would still countdown and remove any 'missing' containers. If the worker ever came back it would still have these containers, but we would not longer be tracking them in the database. Even though we're now garbage collecting these unknown containers, we'd rather that be a last resort. So we fixed it.

🔗 feature

  • @wagdav updated worker heartbeat log level from debug to info to reduce extraneous log output for operators #4606

🔗 fix

  • Fixed a bug where your dashboard search string would end up with +s instead of spaces when logging in. #4265

🔗 fix

  • Fixed a bug where the job page would show a loading spinner forever when there were no builds (like before the job had ever been run) #4636.

🔗 fix

  • Fixed a bug where the tooltip that says 'new version' on a get step on the build page could be hidden underneath the build header #4630.

🔗 fix

  • Fixed a bug where log lines on the build page would have all their timestamps off by one. #4637

🔗 fix

  • @evanchaoli fixed a bug where secret redaction incorrectly "redacts" empty string resulting in mangled logs. #4668

🔗 feature

  • We've restyled the resource metadata displayed in a get step on the build page. It should be easier to read and follow, let us know your critiques on the issue. #4421 #4476

🔗 fix

🔗 fix

🔗 fix

🔗 fix

🔗 fix

  • @ProvoK fixed an issue, that will help resource authors better understand the errors being returned by concourse.

🔗 fix

  • We fixed an issue, introduced in 5.6.0, where checking a resource would fail if the resource and resource type shared the same name.

  • This actually seemed to exacerbate another issue, which we also took the time to fix in #4626.

  • You gotta spend money to make money.

🔗 feature

🔗 fix

  • We fixed a migration from 5.4.0. It only affected a small number users that had old unused resources left over from the ancient times. This probably isn't you, so don't worry.

  • If you ran into this error <3s for being a long time concourse user.

🔗 fix

  • @aledeganopix4d added some lock types that weren't getting emitted as part of our metrics, so that's neat. You might actually see your lock metrics shoot up because of this, don't panic, it's expected.

🔗 fix

  • @evanchaoli fixed a bug where vault users, that hadn't configured a shared path, would end up searching the top level prefix path for secrets.

🔗 fix

  • @evanchaoli fixed yet another bug where the builds api would return the wrong builds if you gave it a date newer than the most recent build.
Assets 14
You can’t perform that action at this time.