Skip to content

build(deps): Bump taskcluster from 24.3.1 to 25.2.0 in /tools #419

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 18, 2020

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps taskcluster from 24.3.1 to 25.2.0.

Release notes

Sourced from taskcluster's releases.

v25.2.0

▶ [minor] bug 1616022 Generic worker now correctly reports its version number. The version number was incorrectly reported in release 25.1.1.

▶ Additional changes not described here: bug 1615762, #2367.

v25.1.1

No changes

v25.1.0

NOTE Release automation for this release failed, so there are no docker images, binaries, or released client libraries.

▶ [minor] bug 1587511 Worker pools that use cloud providers (aws, azure, google) now support a lifecycle.reregistrationTimeout config that will make the credentials we hand to these workers expire within that amount of seconds. If the worker still exists at that time, the instance will be terminated. This lays the groundwork for a subsequent release where you will be able to have your workers reregister to continue working.

v25.0.0

NOTE Release automation for this release failed, so there are no libraries, docker images, or binaries available.

▶ [MAJOR] bug 1608828
Generic worker is now shipped as part of the taskcluster platform release. The generic-worker codebase has been integrated into the monorepo. The former generic-worker github repo is now archived. Consequently, the generic worker version number now matches the taskcluster platform release number. The generic-worker binaries are published to https://github.com/taskcluster/taskcluster/releases.

With this change, the import path for the Taskcluster Go client library changes from github.com/taskcluster/taskcluster/clients/client-go/vNN to github.com/taskcluster/taskcluster/vNN/clients/client-go. Functionality of the library remains unchanged.

▶ [patch] bug 1588099
InsufficientScopes errors now contain a simplfied scope expression describing the missing scopes. In most cases, this will be a single scope.

▶ [patch] bug 1615312
Old generic-worker task directories on POSIX systems (Linux/macOS) are now
deleted more aggressively, by first running chmod u+w -R <task dir> before
running rm -rf <task dir>.

This bug always existed, and could leave files on the filesystem from previous
tasks. Those files were not readable to other task users under the
generic-worker multiuser engine where they were owned by a different OS user,
but they did consume disk space. The files were readable by other tasks under
the generic-worker simple engine, where all tasks run as the same user, but
simple engine is not used for tasks that contain sensitive/private information.

This bug was present in both the simple and multisuer engine, and has been
fixed on both.

Cleanup of Windows task directories will be handled separately in bug
1433854
.

▶ [patch] bug 1608185
The generic-worker binary now accepts a --with-worker-runner argument and expects to interact with worker-runner if that option is given. Otherwise, it will assume it is running alone and will not use any worker-runner features.

▶ Additional changes not described here: bug 1615631, #2312, #2321.

Changelog

Sourced from taskcluster's changelog.

v25.2.0

▶ [minor] bug 1616022 Generic worker now correctly reports its version number. The version number was incorrectly reported in release 25.1.1.

▶ Additional changes not described here: bug 1615762, #2367.

v25.1.1

No changes

v25.1.0

▶ [minor] bug 1587511 Worker pools that use cloud providers (aws, azure, google) now support a lifecycle.reregistrationTimeout config that will make the credentials we hand to these workers expire within that amount of seconds. If the worker still exists at that time, the instance will be terminated. This lays the groundwork for a subsequent release where you will be able to have your workers reregister to continue working.

v25.0.0

▶ [MAJOR] bug 1608828 Generic worker is now shipped as part of the taskcluster platform release. The generic-worker codebase has been integrated into the monorepo. The former generic-worker github repo is now archived. Consequently, the generic worker version number now matches the taskcluster platform release number. The generic-worker binaries are published to https://github.com/taskcluster/taskcluster/releases.

With this change, the import path for the Taskcluster Go client library changes from github.com/taskcluster/taskcluster/clients/client-go/vNN to github.com/taskcluster/taskcluster/vNN/clients/client-go. Functionality of the library remains unchanged.

▶ [patch] bug 1588099 InsufficientScopes errors now contain a simplfied scope expression describing the missing scopes. In most cases, this will be a single scope.

▶ [patch] bug 1615312 Old generic-worker task directories on POSIX systems (Linux/macOS) are now deleted more aggressively, by first running chmod u+w -R <task dir> before running rm -rf <task dir>.

This bug always existed, and could leave files on the filesystem from previous tasks. Those files were not readable to other task users under the generic-worker multiuser engine where they were owned by a different OS user, but they did consume disk space. The files were readable by other tasks under the generic-worker simple engine, where all tasks run as the same user, but simple engine is not used for tasks that contain sensitive/private information.

This bug was present in both the simple and multisuer engine, and has been fixed on both.

Cleanup of Windows task directories will be handled separately in bug 1433854.

▶ [patch] bug 1608185 The generic-worker binary now accepts a --with-worker-runner argument and expects to interact with worker-runner if that option is given. Otherwise, it will assume it is running alone and will not use any worker-runner features.

... (truncated)
Commits
  • e7ac777 v25.2.0
  • 9a831cf Merge pull request #2369 from taskcluster/bug1616022
  • 9181e30 Merge pull request #2368 from taskcluster/issue2367
  • ce49099 Merge pull request #2370 from taskcluster/bug1615762
  • 53de663 Merge pull request #2362 from djmitche/bug1615742
  • f384ba9 Merge pull request #2355 from djmitche/worker-version-ref
  • a73cd80 Bug 1615762 - Specify required version of github.com/tylerb/graceful directly...
  • af35756 Bug 1616022 - fix regexp for updating generic-worker version on release
  • 6ae3d83 Fixed go.mod and go.sum
  • 30500c3 Bug 1615742 - support staging releases
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview dependabot-preview bot added the tools Common Python tools label Feb 18, 2020
@La0 La0 merged commit ff5461e into master Feb 18, 2020
@La0 La0 deleted the dependabot/pip/tools/taskcluster-25.2.0 branch February 18, 2020 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tools Common Python tools
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant