Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[release-4.6] Bug 2020612: Update Jenkins and plugins per 2021-11 advisory #1349

Merged
merged 1 commit into from Nov 22, 2021
Merged

[release-4.6] Bug 2020612: Update Jenkins and plugins per 2021-11 advisory #1349

merged 1 commit into from Nov 22, 2021

Conversation

adambkaplan
Copy link
Contributor

  • Update Jenkins core to 2.303.3 to address critical CVE adivsories
  • Update Subversion plugin to 2.15.1 to address CVE-2021-21698

@adambkaplan
Bug 2020612: Update Jenkins and plugins per 2021-11 advisory
c42fec2 
- Update Jenkins core to 2.303.3 to address critical CVE adivsories
- Update Subversion plugin to 2.15.1 to address CVE-2021-21698
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 19, 2021

@adambkaplan: This pull request references Bugzilla bug 2020612, which is invalid:

  • expected dependent Bugzilla bug 2020613 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

[release-4.6] Bug 2020612: Update Jenkins and plugins per 2021-11 advisory

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot added bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Nov 19, 2021
@adambkaplan
Copy link
Contributor Author

/assign @akram

/cc @coreydaley @prietyc123

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 19, 2021
@gabemontero
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 19, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 19, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adambkaplan, gabemontero

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [adambkaplan,gabemontero]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 20, 2021

@openshift-bot: This pull request references Bugzilla bug 2020612, which is invalid:

  • expected dependent Bugzilla bug 2020613 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-bot
Copy link
Contributor

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2021

@openshift-bot: This pull request references Bugzilla bug 2020612, which is invalid:

  • expected dependent Bugzilla bug 2020613 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-bot
Copy link
Contributor

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 22, 2021

@openshift-bot: This pull request references Bugzilla bug 2020612, which is invalid:

  • expected dependent Bugzilla bug 2020613 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@bparees bparees added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Nov 22, 2021
@bparees
Copy link
Contributor

bparees commented Nov 22, 2021

marking as valid bug based on https://bugzilla.redhat.com/show_bug.cgi?id=2020616 passing verification.

@jitendar-singh
Copy link
Contributor

/cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Nov 22, 2021
@prietyc123
Copy link
Contributor

@coreydaley We need risk assessed label on this pr.

adambkaplan
adambkaplan commented Nov 22, 2021
View reviewed changes
Copy link
Contributor Author

@adambkaplan adambkaplan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/label backport-risk-assessed

  • Subjective assesment has been completed and/or the bug has the "FastFix" keyword.
  • Bug qualifies for backport based on priority, severity, and/or customer impact.
  • Release is fully supported OR one of the following:
    • The bug is a critical fix, no reasonable workaround exists, and a recommendation for upgrade has been ruled out.
    • The bug is a security fix.
  • Bug severity reflects criticality.
  • PR is merged in the next newer release and has been VERIFIED by QE OR bug is FastFix and has been verified in the main development branch.
  • PR has title and description suitable for end user release notes, including BZ identifier, issue impact, cause, and resolution.

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Nov 22, 2021
@openshift-merge-robot openshift-merge-robot merged commit 3c3794f into openshift:release-4.6 Nov 22, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 22, 2021

@adambkaplan: All pull requests linked via external trackers have merged:

Bugzilla bug 2020612 has been moved to the MODIFIED state.

In response to this:

[release-4.6] Bug 2020612: Update Jenkins and plugins per 2021-11 advisory

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@adambkaplan
Copy link
Contributor Author

Installed plugins:

ace-editor:1.1
ant:1.11
apache-httpcomponents-client-4-api:4.5.10-2.0
authentication-tokens:1.4
blueocean-autofavorite:1.2.3
blueocean-bitbucket-pipeline:1.24.4
blueocean-commons:1.24.4
blueocean-config:1.24.4
blueocean-core-js:1.24.4
blueocean-dashboard:1.24.4
blueocean-display-url:2.2.0
blueocean-events:1.24.4
blueocean-github-pipeline:1.24.4
blueocean-git-pipeline:1.24.4
blueocean-i18n:1.24.4
blueocean:1.24.4
blueocean-jwt:1.24.4
blueocean-personalization:1.24.4
blueocean-pipeline-api-impl:1.24.4
blueocean-pipeline-editor:1.24.4
blueocean-pipeline-scm-api:1.24.4
blueocean-rest-impl:1.24.4
blueocean-rest:1.24.4
blueocean-web:1.24.4
bouncycastle-api:2.18
branch-api:2.5.6
cloudbees-bitbucket-branch-source:2.4.4
cloudbees-folder:6.15
conditional-buildstep:1.3.1
config-file-provider:3.7.1
configuration-as-code-groovy:1.1
configuration-as-code:1.47
credentials-binding:1.23
credentials:2.3.15
display-url-api:2.3.4
docker-commons:1.16
docker-workflow:1.23
durable-task:1.35
echarts-api:4.7.0-4
favorite:2.3.1
git-client:3.5.1
github-api:1.114.2
github-branch-source:2.6.0
github:1.33.0
git:4.5.2
git-server:1.7
google-oauth-plugin:1.0.0
groovy:2.2
handlebars:1.1
handy-uri-templates-2-api:2.1.6-1.0
htmlpublisher:1.21
jackson2-api:2.12.1
jenkins-design-language:1.24.4
jira:3.0.17
job-dsl:1.77
jquery3-api:3.5.1-1
jquery-detached:1.2.1
jsch:0.1.55.2
junit:1.30
kubernetes-client-api:4.13.2-1
kubernetes-credentials:0.7.0
kubernetes:1.29.0
lockable-resources:2.10
mailer:1.32.1
mapdb-api:1.0.9.0
matrix-auth:2.6.2
matrix-project:1.18
mercurial:2.12
metrics:4.0.2.6
momentjs:1.1
oauth-credentials:0.3
okhttp-api:3.12.12.2
openshift-client:1.0.34
openshift-login:1.0.26
openshift-sync:1.0.46
pam-auth:1.6
parameterized-trigger:2.36
pipeline-build-step:2.12
pipeline-github-lib:1.0
pipeline-graph-analysis:1.10
pipeline-input-step:2.11
pipeline-milestone-step:1.3.1
pipeline-model-api:1.7.2
pipeline-model-declarative-agent:1.1.1
pipeline-model-definition:1.6.0
pipeline-model-extensions:1.7.2
pipeline-rest-api:2.10
pipeline-stage-step:2.3
pipeline-stage-tags-metadata:1.6.0
pipeline-stage-view:2.10
pipeline-utility-steps:2.5.0
plain-credentials:1.7
plugin-util-api:1.2.2
prometheus:2.0.0
pubsub-light:1.13
run-condition:0.10
scm-api:2.6.4
script-security:1.75
snakeyaml-api:1.27.0
sse-gateway:1.24
ssh-credentials:1.18.1
structs:1.20
subversion:2.15.1
token-macro:2.13
trilead-api:1.0.8
variant:1.4
workflow-aggregator:2.6
workflow-api:2.40
workflow-basic-steps:2.18
workflow-cps-global-lib:2.15
workflow-cps:2.87
workflow-durable-task-step:2.31
workflow-job:2.39
workflow-multibranch:2.22
workflow-remote-loader:1.5
workflow-scm-step:2.11
workflow-step-api:2.23
workflow-support:3.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@coreydaley coreydaley Awaiting requested review from coreydaley

@prietyc123 prietyc123 Awaiting requested review from prietyc123

@akram akram Awaiting requested review from akram

@sbose78 sbose78 Awaiting requested review from sbose78

Assignees

@akram akram

@gabemontero gabemontero

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
8 participants
@adambkaplan @gabemontero @openshift-bot @bparees @jitendar-singh @prietyc123 @akram @openshift-merge-robot