Skip to content

[release-4.4] Bug 1847551: reenable jenkins e2e in e2e-gcp-builds#25128

Merged
openshift-merge-robot merged 1 commit intoopenshift:release-4.4from
openshift-cherrypick-robot:cherry-pick-25033-to-release-4.4
Jun 19, 2020
Merged

[release-4.4] Bug 1847551: reenable jenkins e2e in e2e-gcp-builds#25128
openshift-merge-robot merged 1 commit intoopenshift:release-4.4from
openshift-cherrypick-robot:cherry-pick-25033-to-release-4.4

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #25033

/assign gabemontero

@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: Bugzilla bug 1841315 has been cloned as Bugzilla bug 1847551. Retitling PR to link against new bug.
/retitle [release-4.4] Bug 1847551: reenable jenkins e2e in e2e-gcp-builds

Details

In response to this:

[release-4.4] Bug 1841315: reenable jenkins e2e in e2e-gcp-builds

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-robot openshift-ci-robot changed the title [release-4.4] Bug 1841315: reenable jenkins e2e in e2e-gcp-builds [release-4.4] Bug 1847551: reenable jenkins e2e in e2e-gcp-builds Jun 16, 2020
@openshift-ci-robot openshift-ci-robot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium 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. labels Jun 16, 2020
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: This pull request references Bugzilla bug 1847551, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.4.z) matches configured target release for branch (4.4.z)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1841315 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1841315 targets the "4.5.0" release, which is one of the valid target releases: 4.5.0, 4.5.z
  • bug has dependents
Details

In response to this:

[release-4.4] Bug 1847551: reenable jenkins e2e in e2e-gcp-builds

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.

@gabemontero
Copy link
Copy Markdown
Contributor

/approve

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 16, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 16, 2020
@gabemontero
Copy link
Copy Markdown
Contributor

gabemontero commented Jun 16, 2020

/assign @akram
/assign @waveywaves

when e2e-gcp-builds passes, feel free to lgtm if one of you all likes

I'll ping patch manager about cherrypick approval after that (conveniently for us it is @bparees this week)

Once this merges we can pick the changes besides removing the g.Skip into 4.3.z

@gabemontero
Copy link
Copy Markdown
Contributor

CI bld img flakes

/retest

@gabemontero
Copy link
Copy Markdown
Contributor

OK we have passing jenkins e2e in e2e-gcp-builds https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/25128/pull-ci-openshift-origin-release-4.4-e2e-gcp-builds/1272957974301642752

Found the tests in the successful section

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 16, 2020
@openshift-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gabemontero, openshift-cherrypick-robot

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@bparees bparees added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 18, 2020
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

2 similar comments
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

@openshift-merge-robot openshift-merge-robot merged commit 76f8f44 into openshift:release-4.4 Jun 19, 2020
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged: openshift/origin#25128. Bugzilla bug 1847551 has been moved to the MODIFIED state.

Details

In response to this:

[release-4.4] Bug 1847551: reenable jenkins e2e in e2e-gcp-builds

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.

@gabemontero
Copy link
Copy Markdown
Contributor

/cherrypick release-4.3

@openshift-cherrypick-robot
Copy link
Copy Markdown
Author

@gabemontero: new pull request created: #25171

Details

In response to this:

/cherrypick release-4.3

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.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium 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

Development

Successfully merging this pull request may close these issues.

8 participants