github.com/chenbh/concourse/v6@v6.4.2/release-notes/v5.3.0.md (about)

     1  #### <sub><sup><a name="v530-note-1" href="#v530-note-1">:link:</a></sup></sub> feature
     2  
     3  * @rliebz added the ability for `put` steps to [`git` resource](https://github.com/concourse/git-resource)s with the parameter `merge: true` to be further configured with the parameter `returning: unmerged`, which will ensure that concurrent changes to the same remote branch do not affect downstream jobs concourse/git-resource#262.
     4    
     5    
     6  #### <sub><sup><a name="v530-note-2" href="#v530-note-2">:link:</a></sup></sub> feature
     7  
     8  * Added the option for the [BOSH Backup and Restore](https://docs.cloudfoundry.org/bbr/) database backup job in the [BOSH release](https://github.com/concourse/concourse-bosh-release) to be configured via a [BOSH link](https://bosh.io/docs/links/) concourse/concourse-bosh-release#29, concourse/concourse-bosh-release#35.
     9    
    10    
    11  #### <sub><sup><a name="v530-note-3" href="#v530-note-3">:link:</a></sup></sub> feature
    12  
    13  * @stigtermichiel tuned our build process so that the size of the compressed frontend code is reduced by a factor of 3 - page loads should be accordingly faster concourse/concourse#3915.
    14    
    15    
    16  #### <sub><sup><a name="v530-note-4" href="#v530-note-4">:link:</a></sup></sub> feature
    17  
    18  * If you want your web node to accept encrypted connections over HTTPS, you now have the option of connecting to an [ACME server](https://en.wikipedia.org/wiki/Automated_Certificate_Management_Environment) to automatically retrieve a certificate from an ACME server of your choice. By default it will reach the free public ACME service provided by [Let's Encrypt](https://letsencrypt.org/).
    19    
    20    Thanks to @henderjm for the PR concourse/concourse#3878!
    21    
    22    
    23  #### <sub><sup><a name="v530-note-5" href="#v530-note-5">:link:</a></sup></sub> feature
    24  
    25  * @agurney improved the info api endpoint (`/api/v1/info`) to return both the external URL and cluster name concourse/concourse#3862.
    26    
    27    Hopefully this will enable future improvements to `fly` and the web UI!
    28    
    29    
    30  #### <sub><sup><a name="v530-note-6" href="#v530-note-6">:link:</a></sup></sub> feature
    31  
    32  * @jmccann enabled Concourse to authenticate with [Vault as a credential manager](https://concourse-ci.org/vault-credential-manager.html) via an LDAP backend by setting `CONCOURSE_VAULT_AUTH_PARAM="username:<your ldap username>,password:<your ldap password>"` concourse/concourse#3884.
    33    
    34    
    35  #### <sub><sup><a name="v530-note-7" href="#v530-note-7">:link:</a></sup></sub> feature
    36  
    37  * When you pin a resource through the web UI, your name and current local time will now be automatically added as the pin comment concourse/concourse#3743.
    38    
    39    
    40  #### <sub><sup><a name="v530-note-8" href="#v530-note-8">:link:</a></sup></sub> feature
    41  
    42  * The 'password' field on the login page now has an HTML property that will be ignored by most browsers, but helps Concourse pass some automated security scans concourse/concourse#3839.
    43    
    44    
    45  #### <sub><sup><a name="v530-note-9" href="#v530-note-9">:link:</a></sup></sub> feature
    46  
    47  * @tvon gave the highlighted lines on the build page a slightly darker color so they really pop concourse/concourse#3866.
    48    
    49    
    50  #### <sub><sup><a name="v530-note-10" href="#v530-note-10">:link:</a></sup></sub> fix
    51  
    52  * @palixthepalalix fixed a [bug](https://github.com/concourse/concourse/issues/3794) in the [`git` resource](https://github.com/concourse/git-resource) where commits from extraneous branches could appear in the version history if a tag filter was specified concourse/git-resource#261.
    53    
    54    
    55  #### <sub><sup><a name="v530-note-11" href="#v530-note-11">:link:</a></sup></sub> fix
    56  
    57  * Made the Concourse worker process systemd-aware. This fixed a subtle [bug](https://github.com/concourse/concourse/issues/3613) introduced in [**v5.0.0**](https://github.com/concourse/concourse/releases/tag/v5.0.0) that could, on rare occasions, cause [container limits](https://concourse-ci.org/tasks.html#task-container-limits) not to be enforced or prevent containers from being killed concourse/concourse-bosh-release#24, concourse/concourse-bosh-release#31.
    58    
    59    Thanks to @bodymindarts for contributing to this effort.
    60    
    61    
    62  #### <sub><sup><a name="v530-note-12" href="#v530-note-12">:link:</a></sup></sub> fix
    63  
    64  * Addressed a bug where in rare circumstances, `fly intercept -c` would find multiple check containers for the same resource concourse/concourse#3983.
    65    
    66    
    67  #### <sub><sup><a name="v530-note-13" href="#v530-note-13">:link:</a></sup></sub> fix
    68  
    69  * In service of a [refactor](https://github.com/concourse/concourse/issues/3811), [task caches](https://concourse-ci.org/tasks.html#caches) are now decoupled from the worker(s) they are stored on. As a result, you may find that in multi-worker deployments, pipelines making use of task caches may consume duplicate storage across workers concourse/concourse#3830, concourse/concourse#3965.
    70    
    71    
    72  #### <sub><sup><a name="v530-note-14" href="#v530-note-14">:link:</a></sup></sub> fix
    73  
    74  * Corrected a [surprising behaviour](https://github.com/concourse/concourse/issues/3957) where, when a pipeline was paused for an extended period of time, many of its resources' versions would disappear concourse/concourse#3963.
    75    
    76    
    77  #### <sub><sup><a name="v530-note-15" href="#v530-note-15">:link:</a></sup></sub> fix
    78  
    79  * There was a long-standing [bug](https://github.com/concourse/concourse/issues/1710) on the dashboard, where the existence of circular pipelines would cause the browser to crash. This was fixed in [**v5.2.0**](https://github.com/concourse/concourse/releases/tag/v5.2.0), but the fix caused a [performance regression](https://github.com/concourse/concourse/issues/3748), which is now also fixed concourse/concourse#3870, concourse/concourse#3901.
    80    
    81    
    82  #### <sub><sup><a name="v530-note-16" href="#v530-note-16">:link:</a></sup></sub> fix
    83  
    84  * Fixed a [bug](https://github.com/concourse/concourse/issues/3814), introduced in [**v5.1.0**](https://github.com/concourse/concourse/releases/tag/v5.1.0), where, on a build step with [`attempts:`](https://concourse-ci.org/attempts-step-modifier.html) specified, only one attempt would be possible to view on the build page concourse/concourse#3898.
    85    
    86    
    87  #### <sub><sup><a name="v530-note-17" href="#v530-note-17">:link:</a></sup></sub> fix
    88  
    89  * @gaelL Fixed a [bug](https://github.com/concourse/concourse/issues/3549), which had existed since at least [**v4.2.3**](https://github.com/concourse/concourse/releases/tag/v4.2.3), where operators were prevented from retiring team-scoped workers with the `concourse retire-worker` command concourse/concourse#3929.
    90    
    91    
    92  #### <sub><sup><a name="v530-note-18" href="#v530-note-18">:link:</a></sup></sub> fix
    93  
    94  * A [bug](https://github.com/concourse/concourse/issues/3930) on the reaped build logs screen was fixed, where a link was pointing to deprecated documentation concourse/concourse#3931.
    95    
    96    This screen is visible when you visit a build that is older than its job's configured [retention policy](https://concourse-ci.org/jobs.html#job-build-log-retention).
    97    
    98    
    99  #### <sub><sup><a name="v530-note-19" href="#v530-note-19">:link:</a></sup></sub> fix
   100  
   101  * Fixed a problem with one of the database migrations introduced in [**v5.0.0**](https://github.com/concourse/concourse/releases/tag/v5.0.0) which could cause the web node startup to fail in some cases. This won't affect users who have kept up to date until now, but if this is the first version of Concourse you are deploying since before [**v5.0.0**](https://github.com/concourse/concourse/releases/tag/v5.0.0), the upgrade should be a little more resilient concourse/concourse#3996.
   102    
   103    
   104  #### <sub><sup><a name="v530-note-20" href="#v530-note-20">:link:</a></sup></sub> fix
   105  
   106  * @mockersf fixed a problem where timestamps weren't being properly returned when a get step or a put step finished. This caused some wacky durations to be displayed on build pages concourse/concourse#3871.
   107    
   108    
   109  #### <sub><sup><a name="v530-note-21" href="#v530-note-21">:link:</a></sup></sub> fix
   110  
   111  * Fixed an issue with our build process that caused `fly` to [stop working](https://github.com/concourse/concourse/issues/3691) for some folks making use of a VPN with split DNS.
   112    
   113    
   114  #### <sub><sup><a name="v530-note-22" href="#v530-note-22">:link:</a></sup></sub> fix
   115  
   116  * Fixed a [bug](https://github.com/concourse/concourse/issues/2323) where the dashboard preview of a paused job with a pending build would show the color of the most recent build's status, when it should be blue concourse/concourse#3718.
   117    
   118