buddieslkp.blogg.se - Appid patch v3

This is not a required update for those with externalized environments at this time, but will be when v2.18 is released.

We have updated our software packages to the following versions. Starting in v2.18 it will become required.

It is currently a best practice to use a Services Machine with a minimum of 32GB of RAM.

Fixed issue where workflows were constrained from fanning out to large number of jobs.

Datadog API token field was stored in plaintext, now set as a password field.

We have added more error checking and validation around GitHub’s API so the existing list commit endpoint no longer causes issues.

Previously, caching issues had been experienced when local storage was used rather than the default option of using S3 (selecting None under * Storage Driver options from the Management Console).

Improved performance when using local storage.

Fixed a bug causing duplicate docker networks on same nomad client (if running build using machine:true AND vm-provider=on_host).

Fixed a bug causing Workflows to get stuck when infrastructure_failure happens after a job fails.

Fixed a bug where some commits with in the message were still being built.

The CIRCLE_PULL_REQUEST environment variable was not being populated correctly in all cases when building across forks.

We have optimized our handling of large amounts of build output and test results XML, to avoid out-of-memory errors.

If you are using a context with no names, it will no longer be accessible from your execution environment.

You can no longer create contexts with no names.

Fixed changing the RabbitMQ hostname for Scheduled Workflows when externalizing.

Fixed issue with Scheduled Workflows when the services machine is restarted.

Fixed some bugs related to GitHub API response handling and webhook handling.