Skip to content

Bump pyyaml from 3.12 to 5.1 in /infradb#3

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/pip/infradb/pyyaml-5.1
Closed

Bump pyyaml from 3.12 to 5.1 in /infradb#3
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/pip/infradb/pyyaml-5.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 22, 2019

Copy link
Copy Markdown

Bumps pyyaml from 3.12 to 5.1.

Changelog

Sourced from pyyaml's changelog.

5.1 (2019-03-13)

3.13 (2018-07-05)

  • Resolved issues around PyYAML working in Python 3.7.
Commits
  • e471e86 Updates for 5.1 release
  • 9141e90 Windows Appveyor build
  • d6cbff6 Skip certain unicode tests when maxunicode not > 0xffff
  • 69103ba Update .travis.yml to use libyaml 0.2.2
  • 91c9435 Squash/merge pull request #105 from nnadeau/patch-1
  • 507a464 Make default_flow_style=False
  • 07c88c6 Allow to turn off sorting keys in Dumper
  • 611ba39 Include license file in the generated wheel package
  • 857dff1 Apply FullLoader/UnsafeLoader changes to lib3
  • 0cedb2a Deprecate/warn usage of yaml.load(input)
  • 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 ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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

You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [pyyaml](https://github.com/yaml/pyyaml) from 3.12 to 5.1.
- [Release notes](https://github.com/yaml/pyyaml/releases)
- [Changelog](https://github.com/yaml/pyyaml/blob/master/CHANGES)
- [Commits](yaml/pyyaml@3.12...5.1)

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Oct 22, 2019
@dependabot @github

dependabot Bot commented on behalf of github Mar 25, 2021

Copy link
Copy Markdown
Author

Superseded by #12.

@dependabot dependabot Bot closed this Mar 25, 2021
@dependabot dependabot Bot deleted the dependabot/pip/infradb/pyyaml-5.1 branch March 25, 2021 21:49
ns-codereview pushed a commit that referenced this pull request Sep 1, 2022
Three major improvements:

1. Changes that allow for re-deploying a Docker Stack (to update the
   agent image, say) *without* immediately killing any running Jenkins
   jobs. This comprises the following changes:

- code to entrypoint script (couchbuilder_transition_start.sh) to
  intercept SIGTERM from Docker Swarm, turning it into a "shutdown
  request" (writing a file to /var/run) rather than a hard kill
- added a step in healthcheck to watch for the shutdown request file
  from entrypoint script, and cleanly shut down the agent process when
  requested AND when the Jenkins agent is not executing any jobs
- extended "stop grace period" (the interval from when Swarm will send
  SIGTERM before it sends an unignorable SIGKILL) from 10 seconds to 60
  minutes, to give jobs time to finish
- added memory reservations to CV agents, to prevent Swarm from
  scheduling a replacement container while the original container was
  still executing a job (without this, Swarm started a second container
  on the same node after waiting for a minute)

2. Since "docker stack deploy" now (undocumented!) supports cap_add, I
   was able to finally delete the hacky swarm-launcher approach used in
   the past to start CV agents in privileged containers (required for
   core dumps and gdb to work - see CBD-3740). Now Docker Swarm directly
   manages CV containers just like it does on every other Jenkins. I
   deleted our snapshot of the swarm-launcher Docker image here as well,
   so we aren't tempted to use it again in future. This change did lose
   the slightly nice feature that CV agents had consistent UI names,
   without -hash suffixes. On the other hand, it restored the ability to
   force-restart an agent from the Jenkins UI by deleting the Agent.

2a. Removed the special-case for the CV stackfile in the EC2 packer
    bootstrap; CV agents can work just like everything else now.

3. Added step in healthcheck that verifies with Jenkins master that the
   agent is still online, and kills the container if not. This should
   prevent the situations mentioned in CBD-5081 where an agent is
   Offline according to Jenkins, but the container is still running so
   Swarm can't start a new one.

Only #3 is tracked by a ticket (CBD-5081), but I've put considerable
thought and experimentation over the years into solving the others, #1
in particular. The stars finally aligned to allow a solution.

Going forward, it will be reasonably important to update both
couchbuilder_transition_start.sh and healthcheck.sh together when
updating Jenkins agent container images, as they as now tightly coupled
(at least for containers operating in Docker Swarm / Jenkins Swarm
mode). Also, for the full benefit of #1 on other Jenkins servers, the
corresponding agent Docker Stackfiles will need to be extended to add
the stop grace period and memory reservations.

While I was in there, I also added CONTAINER_TAG to the list of Jenkins
agent labels when creating a new agent. This makes it easy to see
exactly which container image is being used for any given agent.

Change-Id: I4191d9c14362890314e07ee60abd0e1f7c14460c
Reviewed-on: https://review.couchbase.org/c/build-infra/+/179046
Reviewed-by: Blair Watt <blair.watt@couchbase.com>
Tested-by: Chris Hillery <ceej@couchbase.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants