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.

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

Refactors and moves buildConfigs, imageStreams and some other resources #4261

Conversation

mik-dass
Copy link
Contributor

@mik-dass mik-dass commented Nov 26, 2020

What type of PR is this?

/kind code-refactoring
/kind cleanup

What does does this PR do / why we need it:

Refactors and moves buildConfigs, imageStreams and some other resources like deployments etc into new files or existing files.

Which issue(s) this PR fixes:

Fixes part of #4093

PR acceptance criteria:

How to test changes / Special notes to the reviewer:

  • Tests should pass.

…ew files.

It also refactors a few other resources like deployment etc.

Signed-off-by: mik-dass <mrinald7@gmail.com>
@mik-dass
Copy link
Contributor Author

[odo]  ✗  Waiting for component to start [5m]
[odo]  ✗  Failed to start component with name yhjtpr. Error: Failed to create the component: error while waiting for deployment rollout: timeout while waiting for yhjtpr deployment roll out
Deleting project: afzsefccet

/retest

@dharmit
Copy link
Member

dharmit commented Nov 27, 2020

[odo]  ✗  Waiting for component to start [5m]
[odo]  ✗  Failed to start component with name yhjtpr. Error: Failed to create the component: error while waiting for deployment rollout: timeout while waiting for yhjtpr deployment roll out
Deleting project: afzsefccet

/retest

Looks like #3256.

@dharmit
Copy link
Member

dharmit commented Nov 30, 2020

Once again the CI's failing on:

[odo]  ✗  Waiting for component to start [5m]
[odo]  ✗  Failed to start component with name fcaivh. Error: Failed to create the component: error while waiting for deployment rollout: timeout while waiting for fcaivh deployment roll out
Deleting project: mpvdkbglsm 

#3256 😞

Copy link
Member

@dharmit dharmit left a comment

Choose a reason for hiding this comment

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

/approve
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. Required by Prow. label Nov 30, 2020
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dharmit

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:

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. Required by Prow. label Nov 30, 2020
@openshift-bot
Copy link

/retest

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

5 similar comments
@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-merge-robot openshift-merge-robot merged commit cdfa545 into redhat-developer:master Dec 1, 2020
@mik-dass mik-dass deleted the refactor_oc_kube_client branch December 1, 2020 05:47
@rm3l rm3l added the area/refactoring Issues or PRs related to code refactoring label Jun 16, 2023
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. Required by Prow. area/refactoring Issues or PRs related to code refactoring lgtm Indicates that a PR is ready to be merged. Required by Prow.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants