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

OCPBUGS-19311: Unhide the Import From Git Tab on the Add page if Pipelines Operator is installed and BuildConfig is not installed in the cluster #13128

Conversation

Lucifergene
Copy link
Contributor

Fixes:
https://issues.redhat.com/browse/ODC-7379

Solution Description:
Allowed the Import from Git form to show up even if BuildConfig is not installed in the cluster but Pipelines Operator is installed.

Screen shots / Gifs for design review:

Tab-+Add.OKD.9.mp4

Test setup:

  1. Create a cluster without BC
  2. Verify the Import from Git does not show up in the Add Page
  3. Now, install the Pipelines Operator
  4. Verify that it now shows up in the Add page.

Browser conformance:

  • Chrome
  • Firefox
  • Safari
  • Edge

@Lucifergene Lucifergene changed the title Allowed Import from Git form to show up if Pipelines is enabled ODC-7379: Unhide the Import From Git Tab on the Add page if Pipelines Operator is installed and BuildConfig is not installed in the cluster Sep 1, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 1, 2023
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Sep 1, 2023

@Lucifergene: This pull request references ODC-7379 which is a valid jira issue.

In response to this:

Fixes:
https://issues.redhat.com/browse/ODC-7379

Solution Description:
Allowed the Import from Git form to show up even if BuildConfig is not installed in the cluster but Pipelines Operator is installed.

Screen shots / Gifs for design review:

Tab-+Add.OKD.9.mp4

Test setup:

  1. Create a cluster without BC
  2. Verify the Import from Git does not show up in the Add Page
  3. Now, install the Pipelines Operator
  4. Verify that it now shows up in the Add page.

Browser conformance:

  • Chrome
  • Firefox
  • Safari
  • Edge

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 the component/dev-console Related to dev-console label Sep 1, 2023
@Lucifergene
Copy link
Contributor Author

@openshift-ci openshift-ci bot requested review from jerolimov and lokanandaprabhu and removed request for rohitkrai03 and debsmita1 September 1, 2023 16:03
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 1, 2023

@Lucifergene: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 6, 2023

@Lucifergene: "Dad, I'm hungry." Hello, Hungry. I'm Dad.

In response to this:

/joke

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.

Copy link
Member

@jerolimov jerolimov left a comment

Choose a reason for hiding this comment

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

I tested this on a cluster bot and disabled the BuildConfig as described here.

BuildConfig Pipelines Expected Actual OK / NOK
No No No Import from Git Import from Git option isn't shown, /import/ns/christoph shows 404: Page Not Found 👍
Yes No Import from Git without Add Pipelines option Import from Git option is shown and works as expected 👍
No Yes Import from Git that enforce Pipeline usage Import from Git option is shown, the import with Deployment fail with a short "Not found" message. With "Add pipeline" option checked the import works fine 👍 that pipeline isn't enforced will be handled as part of ODC-7386 / PR #13145
Yes Yes Import from Git with Add Pipelines option Import from Git with Add Pipelines option 👍

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 15, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 15, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jerolimov, Lucifergene

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 15, 2023
@jerolimov
Copy link
Member

/label px-approved
/label docs-approved

@openshift-ci openshift-ci bot added px-approved Signifies that Product Support has signed off on this PR docs-approved Signifies that Docs has signed off on this PR labels Sep 15, 2023
@jerolimov
Copy link
Member

/retitle OCPBUGS-19311 Unhide the Import From Git Tab on the Add page if Pipelines Operator is installed and BuildConfig is not installed in the cluster
/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot changed the title ODC-7379: Unhide the Import From Git Tab on the Add page if Pipelines Operator is installed and BuildConfig is not installed in the cluster OCPBUGS-19311 Unhide the Import From Git Tab on the Add page if Pipelines Operator is installed and BuildConfig is not installed in the cluster Sep 18, 2023
@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Sep 18, 2023
@openshift-ci-robot openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 18, 2023
@openshift-ci-robot
Copy link
Contributor

@Lucifergene: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

Fixes:
https://issues.redhat.com/browse/ODC-7379

Solution Description:
Allowed the Import from Git form to show up even if BuildConfig is not installed in the cluster but Pipelines Operator is installed.

Screen shots / Gifs for design review:

Tab-+Add.OKD.9.mp4

Test setup:

  1. Create a cluster without BC
  2. Verify the Import from Git does not show up in the Add Page
  3. Now, install the Pipelines Operator
  4. Verify that it now shows up in the Add page.

Browser conformance:

  • Chrome
  • Firefox
  • Safari
  • Edge

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.

@jerolimov
Copy link
Member

/cherry-pick release-4.14

@openshift-cherrypick-robot

@jerolimov: once the present PR merges, I will cherry-pick it on top of release-4.14 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.14

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.

@jerolimov
Copy link
Member

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@jerolimov: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

/jira refresh

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.

@jerolimov
Copy link
Member

/retitle OCPBUGS-19311: Unhide the Import From Git Tab on the Add page if Pipelines Operator is installed and BuildConfig is not installed in the cluster

@openshift-ci openshift-ci bot changed the title OCPBUGS-19311 Unhide the Import From Git Tab on the Add page if Pipelines Operator is installed and BuildConfig is not installed in the cluster OCPBUGS-19311: Unhide the Import From Git Tab on the Add page if Pipelines Operator is installed and BuildConfig is not installed in the cluster Sep 18, 2023
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 18, 2023
@openshift-ci-robot
Copy link
Contributor

@Lucifergene: This pull request references Jira Issue OCPBUGS-19311, which is invalid:

  • expected the bug to target the "4.15.0" version, but no target version was set

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

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Fixes:
https://issues.redhat.com/browse/ODC-7379

Solution Description:
Allowed the Import from Git form to show up even if BuildConfig is not installed in the cluster but Pipelines Operator is installed.

Screen shots / Gifs for design review:

Tab-+Add.OKD.9.mp4

Test setup:

  1. Create a cluster without BC
  2. Verify the Import from Git does not show up in the Add Page
  3. Now, install the Pipelines Operator
  4. Verify that it now shows up in the Add page.

Browser conformance:

  • Chrome
  • Firefox
  • Safari
  • Edge

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.

@jerolimov
Copy link
Member

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 18, 2023
@openshift-ci-robot
Copy link
Contributor

@jerolimov: This pull request references Jira Issue OCPBUGS-19311, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.0) matches configured target version for branch (4.15.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sanketpathak

In response to this:

/jira refresh

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-merge-robot openshift-merge-robot merged commit 311c52a into openshift:master Sep 18, 2023
6 checks passed
@openshift-ci-robot
Copy link
Contributor

@Lucifergene: Jira Issue OCPBUGS-19311: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-19311 has been moved to the MODIFIED state.

In response to this:

Fixes:
https://issues.redhat.com/browse/ODC-7379

Solution Description:
Allowed the Import from Git form to show up even if BuildConfig is not installed in the cluster but Pipelines Operator is installed.

Screen shots / Gifs for design review:

Tab-+Add.OKD.9.mp4

Test setup:

  1. Create a cluster without BC
  2. Verify the Import from Git does not show up in the Add Page
  3. Now, install the Pipelines Operator
  4. Verify that it now shows up in the Add page.

Browser conformance:

  • Chrome
  • Firefox
  • Safari
  • Edge

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-cherrypick-robot

@jerolimov: new pull request created: #13160

In response to this:

/cherry-pick release-4.14

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
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. component/dev-console Related to dev-console docs-approved Signifies that Docs has signed off on this PR jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants